Method and system for controlled media sharing in a network

ABSTRACT

A method for controlling media sharing among a plurality of nodes in a network. The present method is comprised of availing to the network an instance of media content for sharing among the plurality of nodes by a source node communicatively coupled to the network. The present method further includes decrypting the instance of media content from an encryption local to the source node. The present method further includes encrypting the instance of media content into an intermediate encryption. The present method further includes transferring the instance of media content to a node while the instance of media content is in the intermediate encryption. The node is associated with the network. The decrypting and the encrypting and the transferring are in response to receiving a request for the instance of media content from the node.

RELATED APPLICATIONS

This application is a Continuation of and claims priority to commonlyassigned U.S. patent application Ser. No. 10/443,929, entitled “Methodand System for Controlled Media Sharing in a Network,” by Risan et al.,filed May 21, 2004, and issued as U.S. Pat. No. ______ on ______, whichis incorporated by reference herein in its entirety. This application isrelated to co-pending U.S. patent application Ser. No. ______, AttorneyDocket Number MOMI-012.DIV2, titled “Method and System for ControlledMedia Sharing in a Network,” by Risan et al., filed ______, and relatedto U.S. patent application Ser. No. ______, Attorney Docket NumberMOMI-012.DIV3, titled “Method and System for Controlled Media Sharing ina Network,” by Risan et al., filed ______.

FIELD OF THE INVENTION

The present invention relates to sharing of media within a network. Moreparticularly, the present invention relates to enabling controlled mediasharing between a plurality of nodes in a network.

BACKGROUND OF THE INVENTION

With advancements in hardware and software technology, computers areintegral tools utilized in various applications, such as finance, CAD(computer aided design), manufacturing, health care, telecommunication,education, etc. Further, an enhancement in computer functionality can berealized by communicatively coupling computers together to form anetwork. Within a network environment, computer systems enable users toexchange files, share information stored in common databases, combine orpool resources, communicate via electronic mail (e-mail), and accessinformation on the Internet. Additionally, computers connected to anetwork environment, e.g., the Internet, provide their users access todata and information from all over the world.

Some of the various types of data that a user can access and shareinclude, but are not limited to, text data such as that found in a worddocument, graphical data such as that found in pictures, e.g., JPEGs,GIFs, TIFFs, audio data such as that found in music files, e.g., MP3files, and video data such as that found in moving pictures files, e.g.,MPEG, MOV, and AVI files, to name a few. In fact, nearly any type ofdata can be stored and shared with other computer systems. In manyinstances, the material contained within the various data types iscopyrighted material.

There are many different types of network environments that can beimplemented to facilitate sharing of data between computer systems. Someof the various network environment types include Ethernet,client-server, and wired and/or wireless network environments. A commonutilization of a network environment type is for file sharing, such asin a P2P network or point-to-point network. Most P2P networks rely onbusiness models based upon the transfer and redistribution ofcopyrighted material, e.g., audio files, between computers coupled to anetwork, e.g., the Internet. A P2P network allows a user to acquire thecopyrighted material from a computer, a web site source, or a musicbroadcaster, and store and share the material with other usersthroughout the network, in some instances acting as a web site source ora music broadcaster.

It is also common for users sharing files in an uncontrolled manner touse freely distributed or commercially available media playerapplications to experience, e.g., listen, view, and/or watch, the sharedfiles. In many instances, these media player applications also providefor downloading the media file from a P2P network or from licensed webbroadcasters, saving it locally, and then upload the media file onto anunlawful P2P or similar network and/or consumer recording devices.Unlawfully saving a media file can be as simple as selecting the save orrecord function on a media player application.

Additionally, many of the computers, web sites, and web broadcastersthat share copyrighted material commonly do not control or monitor thefiles being exchanged between computers. Additionally, when web sitesattempt to control or restrict the distribution of copyrighted material,e.g., audio files, users seeking to circumvent controls or restrictionscan, in many cases, simply utilize the recording functionality of amedia player application and save the copyrighted material, rename theparticular audio file, and upload the renamed file, rendering attemptsto control or restrict its distribution moot.

A disadvantage to the uncontrolled sharing of files, more particularlythe downloading, saving, and uploading of copyrighted material, e.g.,music files, is that there is currently no effective means to providecompensation to the owner (e.g., record company, lyricist, musician,etc.) of the copyrighted material. Studies have revenue losses in thebillions due to unauthorized copying and inaccurate reporting ofroyalties.

Current methods of sharing music files do not provide adequate filedistribution controls or proper accountability with regard to licensingagreements and/or copyright restrictions associated with sharedcopyrighted material.

Additionally, the media file copyright holders are being sold on thepremise that a degraded media file is better than the original becauseyou can't control the original on the computer. Therefore, users may beless likely to use a computer to record/capture/reproduce a poor qualityversion. Once the user does capture the media file, it is a mediocresounding copy. This fundamental concept of recording companies giving aless than ideal data version is in the hope that the lack of soundquality will deter users from recording, copying, etc., the media files.

Applications are readily available via the Internet for the expresspurpose of producing an exact audio copy of media files. One example isExact Audio Copy, a freeware software program freely available on theInternet which produces an exact audio copy in .wav file format.Additionally, there are “ripping” applications, readily available viathe Internet, that goes to the audio tracks where it can “rip” the audioor video file.

Further, many of the media player/recorder applications are designed tocapture and record incoming media files in a manner that circumventscontrols implemented by a media player application inherent to anoperating system, e.g., QuickTime for Apple, MediaPlayer for Windows™,etc., or downloadable from the Internet, e.g., RealPlayer, LiquidAudio,or those provided by webcasters, e.g., PressPlay, for controllingunauthorized recording of media files. Also, many digital recordingdevices, e.g., mini-disc recorders, MP3 recorders, and the like, can becoupled to a digital output of a computer system, e.g., a USB port, aS/Pdif out, and the like, to capture the media file.

It is desired to prevent recording applications, such as Total Recorder,Sound Forge, and numerous others, that are adapted to establish aconnection with a kernel level driver operable within an operatingsystem to capture and redirect the media file to create an unauthorizedreproduction of a media file. It is also desired to prevent recordingapplications from accessing a kernel-mode media device driver and makingunauthorized copies of copyrighted material through some availablenetwork, e.g., wireline, wireless, P2P, etc., or through a communicativecoupling. It is further desirable to prevent access to a kernel basedmedia device driver by a recording application for the purpose of makingunauthorized copies of media files from or to alternative sources, e.g.,CD players, DVD players, removable hard drives, personal electronicand/or recording devices, e.g., MP3 recorders, and the like.

Current methods of controlling the sharing of media between a pluralityof nodes in a network environment are inadequate.

SUMMARY OF THE INVENTION

Accordingly, a need exists for a method and system that controls sharingof media between a plurality of computer systems in a network.Embodiments of the present invention satisfy the above mentioned needs.

In one embodiment, a method for controlling media sharing among aplurality of nodes in a network is described. The present method iscomprised of availing to the network an instance of media content forsharing among the plurality of nodes by a source node communicativelycoupled to the network. The present method further includes decryptingthe instance of media content from an encryption local to the sourcenode. The present method further includes encrypting the instance ofmedia content into an intermediate encryption. The present methodfurther includes transferring the instance of media content to a nodewhile the instance of media content is in the intermediate encryption.The node is associated with the network. The decrypting and theencrypting and the transferring are in response to receiving a requestfor the instance of media content from the node.

In another embodiment, another method of controlled media sharing amonga plurality of nodes in a network is described. The present method iscomprised of initiating a search for an instance of media contentavailable from the network. A node communicatively coupled with thenetwork initiates said search. The present method further includesreceiving a source location of the instance of media content from anadministrative node coupled to the network. The present method furtherincludes requesting from the source location the instance of mediacontent. The present method further includes receiving the instance ofmedia content from the location. The instance of media content isdecrypted from an encryption local to the source location and encryptedin an intermediate encryption prior to delivery to the node.

In yet another embodiment, another method for controlled media sharingamong a plurality of nodes in a network is described. The present methodis comprised of transmitting a location of a source node having aninstance of media content to a node requesting the instance of mediacontent. The source node is communicatively coupled with the network.The transmitting is in response to the network receiving a request forthe instance of media content. The present method further includesreceiving from the source node a request for an intermediate encryptionkey to encrypt the instance of media content with an intermediateencryption. The present method further includes sending the intermediateencryption key to the source node, enabling the source node to decryptthe instance of media content from an encryption local to the sourcenode and to encrypt the instance of media content into the intermediateencryption for transfer. The present method further includes receivingan acknowledgement indicator indicating successful receipt of theinstance of media content by the node.

In still another embodiment, another method of controlled media sharingamong a plurality of nodes in a network is described. The present methodis comprised of transmitting an instance of media content from a sourcenode to a node. The source node, the node, and an administrative nodeare communicatively coupled to the network. The present method furtherincludes transmitting from the node to the administrative node anindicator for indicating a successful transfer of the instance of mediacontent from the source node to the node. The present method furtherincludes generating a transaction applicable to the node and associatedwith the instance of media content for the transmission of the instanceof media content to the node. The transaction generation is performed bythe administrative node. The node and the source node are currentlyassociated with the network.

These and other objects and advantages of the present invention will nodoubt become obvious to those of ordinary skill in the art after havingread the following detailed description of the preferred embodimentswhich are illustrated in the various drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form a part ofthis specification, illustrate embodiments of the invention and,together with the description, serve to explain the principles of theinvention.

FIG. 1 is a block diagram of an exemplary computer system that can beutilized in accordance with an embodiment of the present invention.

FIG. 2 is a block diagram of an exemplary network environment that canbe utilized in accordance with an embodiment of the present invention.

FIG. 3 is a block diagram of various exemplary functional components ofa copyright compliance mechanism in accordance with an embodiment of thepresent invention.

FIG. 4 is an illustration of an exemplary system for implementing acopyright compliance mechanism in accordance with an embodiment of thepresent invention.

FIG. 5A is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized recording ofmedia files, in accordance with one embodiment of the present invention.

FIG. 5B is a data flow block diagram showing an implementation of acomponent of a copyright compliance mechanism for preventingunauthorized recording of media files, in accordance with anotherembodiment of the present invention.

FIG. 5C is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized output ofmedia files, in accordance with one embodiment of the present invention.

FIG. 5D is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized output ofmedia files through media file capture at a kernel level, in accordancewith one embodiment of the present invention.

FIG. 6A is a block diagram of an environment for preventing unauthorizedcopying of a media file, in accordance with one embodiment of thepresent invention.

FIGS. 7A, 7B, and 7C are a flowchart of steps performed in accordancewith an embodiment of the present invention for providing a copyrightcompliance mechanism to a network of client and server computer systems.

FIG. 8 is a diagram of an exemplary global media delivery system inwhich a copyright compliance mechanism can be implemented in accordancewith an embodiment of the present invention.

FIG. 9 is a block diagram of components of a copyright compliancemechanism installable from a media storage device upon which protectedmedia files are disposed, in accordance with one embodiment of thepresent invention.

FIG. 10 is a block diagram of a communicative environment for dynamicupdating of a copyright compliance mechanism installed from a mediastorage device onto a client computer system, in accordance with oneembodiment of the present invention.

FIG. 11 is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized reproductionof a protected media file located on a media storage device, inaccordance with one embodiment of the present invention.

FIG. 12 is a block diagram of components of a usage compliance mechanisminstallable from a media storage device upon which protected media filesare disposed, in accordance with one embodiment of the presentinvention.

FIG. 13 is a block diagram of components of a usage compliance mechanismand content disposed on a media storage device, in accordance with oneembodiment of the present invention.

FIG. 14 is a block diagram of a communicative environment forcontrolling presentation of content on a media storage device, inaccordance with one embodiment of the present invention.

FIG. 15 is a data flow block diagram showing an implementation of ausage compliance mechanism for controlling presentation of contentdisposed on a media storage device, in accordance with one embodiment ofthe present invention.

FIG. 16 is a flowchart of a process for controlling presentation ofcontent disposed on a media storage device, in accordance with oneembodiment of the present invention.

FIG. 17 is a block diagram of a network environment for sharing mediacontent among nodes within the network in accordance with one embodimentof the present invention.

FIG. 18 is a block diagram of components within an exemplary usagecompliance mechanism configured for utilization in a distributed networktopology for controlling media sharing among computer systems in thenetwork, in accordance with one embodiment of the present invention.

FIG. 19 is an illustrated data flow of an exemplary system forcontrolling media sharing among multiple computer systemscommunicatively coupled in a network in accordance with one embodimentof the present invention.

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments of the invention,examples of which are illustrated in the accompanying drawings. Whilethe invention will be described in conjunction with embodiments, it willbe understood that they are not intended to limit the invention to theseembodiments. On the contrary, the invention is intended to coveralternatives, modifications, and equivalents, which may be includedwithin the spirit and scope of the invention as defined by the appendedclaims. Furthermore, in the following detailed description of thepresent invention, numerous specific details are set forth in order toprovide a thorough understanding of the present invention. However, toone of ordinary skill in the art, the present invention may be practicedwithout these specific details. In other instances, well known methods,procedures, components, and circuits have not been described in detailas not to unnecessarily obscure aspects of the present invention.

Some portions of the detailed description which follows are presented interms of procedures, logic blocks, processing, and other symbolicrepresentations of operations on data bits within a computing system ordigital memory system. These descriptions and representations are themeans used by those skilled in the data processing art to mosteffectively convey the substance of their work to others skilled in theart. A procedure, logic block, process, etc., is herein, and generally,conceived to be a self-consistent sequence of steps or instructionsleading to a desired result. The steps are those involving physicalmanipulations of physical quantities. Usually, though not necessarily,these physical manipulations take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared, andotherwise manipulated in a computing system or similar electroniccomputing device. For reasons of convenience, and with reference tocommon usage, these signals are referred to as bits, values, elements,symbols, characters, terms, numbers, or the like, with reference to thepresent invention.

It should be borne in mind, however, that all of these terms are to beinterpreted as referencing physical manipulations and quantities and aremerely convenient labels and are to be interpreted further in view ofterms commonly used in the art. Unless specifically stated otherwise asapparent from the following discussions, it is understood thatdiscussions of the present invention refer to actions and processes of acomputing system, or similar electronic computing device thatmanipulates and transforms data. The data is represented as physical(electronic) quantities within the computing system's registers andmemories and is transformed into other data similarly represented asphysical quantities within the computing system's memories or registers,or other such information storage, transmission, or display devices.

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. To one skilled in the art, thepresent invention may be practiced without these specific details. Inother instances, well-known structures and devices are shown in blockdiagram form in order to avoid obscuring the present invention.

Embodiments of the present invention are discussed primarily in thecontext of a network of computer systems such as a network of desktop,workstation, laptop, handheld, and/or other portable electronic device.For purposes of the present application, the term “portable electronicdevice” is not intended to be limited solely to conventional handheld orportable computers. Instead, the term “portable electronic device” isalso intended to include many mobile electronic devices. Such mobiledevices include, but are not limited to, portable CD players, MP3players, mobile phones, portable recording devices, satellite radios,portable video playback devices (digital projectors), personal videoeyewear, and other personal digital devices. Additionally, embodimentsof the present invention are also well suited for implementation withtheater presentation systems for public and/or private presentation intheaters, auditoriums, convention centers, etc.

FIG. 1 is a block diagram illustrating an exemplary computer system 100that can be used in accordance with an embodiment of the presentinvention. It is noted that computer system 100 can be nearly any typeof computing system or electronic computing device including, but notlimited to, a server computer, a desktop computer, a laptop computer, orother portable electronic device. Within the context of the presentinvention, certain discussed processes, procedures, and steps arerealized as a series of instructions (e.g., a software program) thatreside within computer system memory units of computer system 100 andwhich are executed by a processor(s) of computer system 100, in oneembodiment. When executed, the instructions cause computer system 100 toperform specific actions and exhibit specific behavior which isdescribed in detail herein.

Computer system 100 of FIG. 1 comprises an address/data bus 110 forcommunicating information, one or more central processors 101 coupled tobus 110 for processing information and instructions. Centralprocessor(s) 101 can be a microprocessor or any alternative type ofprocessor. Computer system 100 also includes a computer usable volatilememory 102, e.g., random access memory (RAM), static RAM (SRAM), dynamicRAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate RAM (DDRRAM), etc., coupled to bus 110 for storing information and instructionsfor processor(s) 101. Computer system 100 further includes a computerusable non-volatile memory 103, e.g., read only memory (ROM),programmable ROM, electronically programmable ROM (EPROM), electricallyerasable ROM (EEPROM), flash memory (a type of EEPROM), etc., coupled tobus 110 for storing static information and instructions for processor(s)101. In one embodiment, non-volatile memory 103 can be removable.

System 100 also includes one or more signal generating and receivingdevices, e.g., signal input/output device(s) 104 coupled to bus 110 forenabling computer 100 to interface with other electronic devices.Communication interface 104 can include wired and/or wirelesscommunication functionality. For example, in one embodiment,communication interface 104 is a serial communication port, but canalternatively be one of a number of well known communication standardsand protocols, e.g., a parallel port, an Ethernet adapter, a FireWire(IEEE 1394) interface, a Universal Serial Bus (USB), a small computersystem interface (SCSI), an infrared (IR) communication port, aBluetooth wireless communication adapter, a broadband connection, asatellite link, an Internet feed, a cable modem, and the like. Inanother embodiment, a digital subscriber line (DSL) can be implementedas signal input/output device 104. In such an instance, communicationinterface 104 may include a DSL modem.

Computer 100 of FIG. 1 can also include one or more computer usable datastorage device(s) 108 coupled to bus 110 for storing instructions andinformation, in one embodiment of the present invention. In oneembodiment, data storage device 108 can be a magnetic storage device,e.g., a hard disk drive, a floppy disk drive, a zip drive, or othermagnetic storage device. In another embodiment, data storage device 108can be an optical storage device, e.g., a CD (compact disc), a DVD(digital versatile disc), or other alternative optical storage device.Alternatively, any combination of magnetic, optical, and alternativestorage devices can be implemented, e.g., a RAID (random array ofindependent disks or random array of inexpensive discs) configuration.It is noted that data storage device 108 can be located internal and/orexternal of system 100 and communicatively coupled with system 100utilizing wired and/or wireless communication technology, therebyproviding expanded storage and functionality to system 100. It isfurther noted that nearly any portable electronic device, e.g., device100 a, can also be communicatively coupled with system 100 viautilization of wired and/or wireless technology, thereby expanding thefunctionality of system 100.

System 100 can also include an optional display device 105 coupled tobus 110 for displaying video, graphics, and/or alphanumeric characters.It is noted that display device 105 can be a CRT (cathode ray tube), athin CRT (TCRT), a liquid crystal display (LCD), a plasma display, afield emission display (FED), video eyewear, a projection device (e.g.,an LCD or DLP projector, a movie theater projection system, and thelike.), or any other display device suitable for displaying video,graphics, and alphanumeric characters recognizable to a user.

Computer system 100 of FIG. 1 further includes an optional alphanumericinput device 106 coupled to bus 110 for communicating information andcommand selections to processor(s) 101, in one embodiment. Alphanumericinput device 106 is coupled to bus 110 and includes alphanumeric andfunction keys. Also included in computer 100 is an optional cursorcontrol device 107 coupled to bus 110 for communicating user inputinformation and command selections to processor(s) 101. Cursor controldevice 107 can be implemented using a number of well known devices suchas a mouse, a trackball, a track pad, a joy stick, a optical trackingdevice, a touch screen, etc. It is noted that a cursor can be directedand/or activated via input from alphanumeric input device 106 usingspecial keys and key sequence commands. It is further noted thatdirecting and/or activating the cursor can be accomplished byalternative means, e.g., voice activated commands, provided computersystem 100 is configured with such functionality.

FIG. 2 is a block diagram of an exemplary network 200 in whichembodiments of the present invention may be implemented. In one example,network 200 enables one or more authorized client computer systems(e.g., 210, 220, and 230), each of which are coupled to Internet 201, toreceive media content from a media content server, e.g., 251, via theInternet 201 while preventing unauthorized client computer systems fromaccessing media stored in a database of content server 251.

Network 200 includes a web server 250 and a content server 251 which arecommunicatively coupled to Internet 201. Further, web server 250 andcontent server 251 can be communicatively coupled without utilizingInternet 201, as shown. Web server 250, content server 251, and clientcomputers 210, 220, and 230 can communicate with each other. It is notedthat computers and servers of network 200 are well suited to becommunicatively coupled in various implementations. For example, webserver 250, content server 251, and client computer systems 210, 220,and 230 of network 200 can be communicatively coupled via wiredcommunication technology, e.g., twisted pair cabling, fiber optics,coaxial cable, etc., or wireless communication technology, or acombination of wired and wireless communication technology.

Still referring to FIG. 2, it is noted that web server 250, contentserver 251, and client computer systems 210, 220 and 230 of network 200can, in one embodiment, be each implemented in a manner similar tocomputer system 100 of FIG. 1. However, the server and computer systemsin network 200 are not limited to such implementation. Additionally, webserver 250 and content server 251 can perform various functionalitieswithin network 200. It is also noted that, in one embodiment, web server250 and content server 251 can both be disposed on a single or aplurality of physical computer systems, e.g., computer system 100 ofFIG. 1.

Further, it is noted that network 200 can operate with and deliver anytype of media content, (e.g., audio, video, multimedia, graphics,information, data, software programs, etc.) in any format. In oneexample, content server 251 can provide audio and video files to clientcomputers 210-230 via Internet 201.

FIG. 3 is a block diagram of an exemplary copyright compliance mechanism(CCM) 300, for controlling distribution of, access to, and/or copyrightcompliance of media files, in accordance with an embodiment of thepresent invention. In one embodiment, CCM 300 contains one or moresoftware components and instructions for enabling compliance with DMCA(digital millennium copyright act) restrictions and/or RIAA (recordingindustry association of America) licensing agreements regarding mediafiles. Additionally, CCM 300's software components and instructionsfurther enable compliance with international recording restrictions suchas those defined by the IFPI (international federation of phonographicindustry) and/or the ISRC (international standard recording industry)and/or other foreign or international recording associations and/orforeign or international licensing restrictions. In one embodiment, CCM300 may be integrated into existing and/or newly developed media playerand recorder applications. In another embodiment, CCM 300 may beimplemented as stand alone but in conjunction with existing mediaplayer/recorder applications, such that CCM 300 is communicativelycoupled to existing media player/recorder applications. Alternatively,CCM 300 can be installed as a stand alone mechanism within a clientcomputer system 210. Additionally, CCM 300 can be installed as a standalone mechanism and/or as part of a bundled application from a mediastorage device, e.g., a CD, a DVD, an SD (secure digital card), and/oras part of an installation package. In another example, CCM 300 can beinstalled in conjunction with a presentation of desired media content,e.g., listening to an audio file on a music CD, reading a document,viewing a video, etc. It is noted that, in one embodiment, CCM 300 maybe installed on client system 210 in a clandestine manner, relative to auser.

There are currently two types of copyright licenses recognized by thedigital millennium copyright act (DMCA) for the protection ofbroadcasted copyrighted material. One of the broadcast copyrightlicenses is a compulsory license, also referred to as a statutorylicense. A statutory license is defined as a non-interactive license,meaning the user cannot select the song. Further, a caveat of this typeof broadcast license is that a user must not be able to select aparticular music file for the purpose of recording it to the user'scomputer system or other storage device. Another caveat of a statutorylicense is that a media file is not available more than once for a givenperiod of time. In one example, the period of time can be three hours.

The other type of broadcast license recognized by the DMCA is aninteractive licensing agreement. An interactive licensing agreement iscommonly with the copyright holder, e.g., a record company, the artist,where the copyright holder grants permission for a server, e.g., webserver 250 and/or content server 251 of FIG. 2 to broadcast copyrightedmaterial. Under an interactive licensing agreement, there are a varietyof ways that copyrighted material, e.g., music files, can be broadcast.For example, one manner in which music files can be broadcast is toallow the user to select and listen to a particular sound recording, butwithout the user enabled to make a sound recording. This is commonlyreferred to as an interactive with “no save” license, meaning that theend user is unable to save or store the media content file in arelatively permanent manner. Additionally, another manner in which musicfiles can be broadcast is to allow a user to not only select and listento a particular music file, but additionally allow the user to save thatparticularly music file to disc and/or burn the music file to CD, MP3player, or other portable electronic device. This is commonly referredto as an interactive with “save” license, meaning that the end user isenabled to save, store, or burn to CD, the media content file.

It is noted that the DMCA allows for the “perfect” reproduction of thesound recording. A perfect copy of a sound recording is a one-to-onemapping of the original sound recording into a digitized form, such thatthe perfect copy is virtually indistinguishable and/or has no audibledifferences from the original recording.

In one embodiment, CCM (copyright compliance mechanism) 300 can bestored in web 20 server 250 and/or content server 251 of network 200 andis configured to be installed into each client computer system, e.g.,210, 220 and 230, enabled to access the media files stored withincontent server 251 and/or web server 250. Alternatively, copyrightcompliance mechanism 300 can be externally disposed and communicativelycoupled with a client computer system 200 via, e.g., a portable mediadevice 100a of FIG. 1. In yet another embodiment, CCM 300 can beconfigured to be operable from a media storage device upon which mediafiles may be disposed.

Copyright compliance mechanism 300 is configured to be operable whilehaving portions of components, entire components, combinations ofcomponents, disposed within one or more memory units and/or data storagedevices of a computer system, e.g., 210, 220, and/or 230.

Additionally, portions of components, entire components and/orcombinations of components of CCM 300 can be readily updated, e.g., viaInternet 201, to reflect changes or developments in the DMCA, changes ordevelopments in copyright restrictions and/or licensing agreements thatpertain to any media file, changes in current media player applicationsand/or the development of new media player applications, or tocounteract subversive and/or hacker-like attempts to unlawfully obtainone or more media files.

Referring to FIG. 3, in one embodiment, CCM 300 is shown to includeinstructions 301 for enabling client computer system 210 to interactwith web server 250 and content server 251 of network 200. Instructions301 enable client computer system 210 to interact with servers, e.g.,250 and 251 in a network, e.g., 200.

The copyright compliance mechanism 300 also includes, in one embodiment,a user ID generator 302, for generating a user ID or user key, and oneor more cookie(s) which contain(s) information specific to the user andthe user's computer system, e.g., 210. In one embodiment, the user IDand the cookie(s) are installed in computer system 210 prior toinstallation of the remaining components of the copyright compliancemechanism 300. It is noted that the presence of a valid cookie(s) and avalid user ID/user key are verified by web server 250 before theremaining components of a CCM 300 can be installed, within oneembodiment of the present invention. Additionally, the user ID/user keycan contain, but is not limited to, the user's name, the user's address,the user's credit card number, an online payment account number, averified email address, and an identity (username) and password selectedby the user.

Furthermore, the cookie can contain, but is not limited to, informationspecific to the user, information regarding the user's computer system210, e.g., types of media applications operational therewithin, a uniqueidentifier associated with computer system 210, e.g., a MAC (machineaddress code) address, an IP address, and/or the serial number of thecentral processing unit (CPU) operable on computer system 210 and otherinformation specific to the user and the computer system operated by theuser.

Additionally, in another embodiment, user biometrics may be combinedwith computer system 210 data and user data and incorporated into thegeneration of a user ID. Alternatively, biometric data may be used in astand alone implementation in the generation of the user ID. Types ofbiometric data that may be utilized to provide a user ID and/orauthorization may include, but is not limited to, fingerprint data,retinal scan data, handprint data, facial recognition data, and thelike.

It is noted that the information regarding the client computer system,e.g., 210, the user of system 210, and an access key described hereincan be collectively referred to as authorization data.

Advantageously, with information regarding the user and the user'scomputer system, e.g., 210, web server 250 can determine when a user ofone computer system, e.g., 210, has given their username and password toanother user using another computer system, e.g., 220. Because theusername, password, and the user's computer system 210 are closelyassociated, web server 250 can prevent unauthorized access tocopyrighted media content, in one embodiment. It is noted that if webserver 250 detects unauthorized sharing of usernames and passwords, itcan block the user of computer system 210, as well as other users whounlawfully obtained the username and password, from future access tocopyrighted media content available through web server 250. Web server250 can invoke blocking for any specified period of time, e.g., for amatter of minutes or hours to months, years, or longer.

Still referring to FIG. 3, copyright compliance mechanism 300 furtherincludes one or more coder/decoders (codec) 303 that, in one embodiment,is/are adapted to perform, but is/are not limited to, encoding/decodingof media files, compressing/decompressing of media files, detecting thatdelivered media files are encrypted as prescribed by CCM 300. In thepresent embodiment, coder/decoder 303 can also extract key fields from aheader attached to each media content file for, in part, verificationthat the file originated from a content server, e.g., 251.

In the present embodiment, coder/decoder 303 can also perform a periodicand repeated check of the media file, while the media file is passed tothe media player application, e.g., in a frame by frame basis or in abuffer by buffer basis, to ensure that CCM 300 rules are being enforcedat any particular moment during media playback. It is noted thatdiffering coder/decoders 303 can be utilized in conjunction with varioustypes of copyrighted media content including, but not limited to, audiofiles, video files, graphical files, alphanumeric files and the like,such that any type of media content file can be protected in accordancewith embodiments of the present invention.

With reference still to FIG. 3, copyright compliance mechanism 300 alsoincludes one or more agent programs 304 which are configured to engagein dialogs and negotiate and coordinate transfer of information betweena computer system, e.g., 210, 220, or 230, a server, e.g., web server250 and/or content server 251, and/or media player applications, with orwithout recording functionality, that are operable within a clientcomputer system, in one embodiment. In the present embodiment, agentprogram 304 can also be configured to maintain system state, verify thatother components are being utilized simultaneously, to be autonomouslyfunctional without knowledge of the client, and can also presentmessages, e.g., error messages, media information, advertising, etc.,via a display window or electronic mail. This enables detection ofproper skin implementation and detection of those applications that arerunning. It is noted that agent programs are well known in the art andcan be implemented in a variety of ways in accordance with the presentembodiment.

Copyright compliance mechanism 300 also includes one or more systemhooks 305, in one embodiment of the present invention. A system hook 305is, in one embodiment, a library that is installed in a computer system,e.g., 210, and intercepts system wide events. For example, a system hook305, in conjunction with skins 306, can govern certain properties and/orfunctionalities of media player applications operating within the clientcomputer system, e.g., 210, including, but not limited to, mouse clickshortcuts, keyboard shortcuts, standard system accelerators, progressbars, save functions, pause functions, rewind functions, skip trackfunctions, forward track preview, copying to CD, copying to a portableelectronic device, and the like.

It is noted that the term govern or governing, for purposes of thepresent invention, can refer to a disabling, deactivating, enabling,activating, etc., of a property or function. Governing can also refer toan exclusion of that function or property, such that a function orproperty may be operable but unable to perform in the manner originallyintended. For example, during playing of a media file, the progress barmay be selected and moved from one location on the progress line toanother without having an effect on the play of the media file.

It is further noted that codec 303 compares the information for themedia player application operating in client computer system, e.g., 210,with a list of “signatures” associated with known media recordingapplications. In one embodiment, the signature can be, but is notlimited to being, a unique identifier of a media player application andwhich can consist of the window class of the application along with aproduct name string which is part of the window title for theapplication. Advantageously, when new media player applications aredeveloped, their signatures can be readily added to the signature listvia an update of CCM 300 described herein.

The following C++ source code is exemplary implementation of the portionof a codec 303 for performing media player application detection, inaccordance with an embodiment of the present invention. In anotherembodiment, the following source code can be modified to detect kernelstreaming mechanisms operable within client system 210.

int IsRecorderPresent(TCHAR * szAppClass,   TCHAR * szProdName) {  TCHAR szWndText[_MAX_PATH];       /* buffer to receive title string forwindow */  HWND   hWnd;  /* handle to target window for operation */ int  nRetVal;  /*return value for operation */  /* initialize variables*/  nRetVal = 0;  if ( _tcscmp(szAppClass, _T(“#32770”))   == 0)  {   /*attempt to locate dialog box with specified window title */   if (FindWindow((TCHAR *) 32770, szProdName)    != (HWND) 0)   {    /*indicate application found */    nRetVal = 1;   }  }  else  {   /*attempt to locate window with specified class */   if ( (hWnd =FindWindow(szAppClass, (LPCTSTR) 0))    != (HWND) 0)   {    /* attemptto retrieve title string for window */    if ( GetWindowText(hWnd,      szWndText,       _MAX_PATH)     != 0)    {     /* attempt tolocate product name within title string */     if ( _tcsstr(szWndText,szProdName)      != (TCHAR *) 0)     {      /* indicate applicationfound */      nRetVal = 1;     }    }   }  }  /* return to caller */ return nRetVal; }

It is further noted that codec 303 can also selectively suppresswaveform input/output operations to prevent recording of copyrightedmedia on a client computer system 210. For example, codec 303,subsequent to detection of bundled media player applications operationalin a client computer system, e.g., 210, can stop or disrupt the playingof a media content file. This can be accomplished, in one embodiment, byredirecting and/or diverting certain data pathways that are commonlyused for recording, such that the utilized data pathway is governed bythe copyright compliance mechanism 300. In one embodiment, this can beperformed within a driver shim, e.g., wave driver shim 309 of FIGS. 5Aand 5B.

A driver shim can be utilized for nearly any software output device,e.g., a standard Windows™ waveform output device, e.g., Windows™ MediaPlayer, or hardware output device, e.g., speakers or headphones. Clientcomputer system 210 is configured such that the driver shim (e.g., 309of FIGS. 5A, 5B, 5C, and 5D) will appear as the default waveform mediadevice to client level application programs. Thus, requests forprocessing of waveform media input and/or output will pass through thedriver shim prior to being forwarded to the actual waveform audiodriver, media device driver 505 of FIGS. 5A and 5B. Such waveforminput/output suppression can be triggered by other components of CCM300, e.g., agent 304, to be active when a recording operation isinitiated by a client computer system, e.g., 210, during the play backof media files which are subject to the DMCA.

It is noted that alternative driver shims can be implemented for nearlyany waveform output device including, but not limited to, a Windows™Media Player. It is further noted that the driver shim can beimplemented for nearly any media in nearly any format including, but notlimited to, audio media files and audio input and output devices, video,graphic and/or alphanumeric media files and video input and outputdevices.

The following C++ source code is an exemplary implementation of aportion of a codec 303 and/or a custom media device driver 307 fordiverting and/or redirecting certain data pathways that are commonlyused for recording of media content, in accordance with an embodiment ofthe present invention.

DWORD _stdcallπ widMessage(UINT    uDevId,    UINT     uMsg,    DWORDdwUser,    DWORD dwParam1,    DWORD dwParam2) {   BOOL bSkip;   /* flagindicating operation to be skipped */   HWND  hWndMon;  /* handle tomain window for monitor */   DWORD  dwRetVal;  /* return value foroperation */   /* initialize variables */   bSkip  = FALSE;   dwRetVal =(DWORD) MMSYSERR_NOTSUPPORTED;   if (uMsg == WIDM_START)   {    /*attempt to locate window for monitor application */    if ( (hWndMon =FindMonitorWindow( ))     != (HWND) 0)    { /* obtain setting for driver*/ bDrvEnabled = ( SendMessage(hWndMon,           uiRegMsg,           0,            0)        == 0)      ? FALSE : TRUE; }    if(bDrvEnabled == TRUE)    { /* indicate error in operation */ dwRetVal =MMSYSERR_NOMEM; /* indicate operation to be skipped */ bSkip = TRUE;   }   }   if (bSkip == FALSE)   {    /* invoke entry point for originaldriver */    dwRetVal = CallWidMessage(uDevId, uMsg,    dwUser,dwParam1, dwParam2);   }   /* return to caller */   return dwRetVal; }

It is noted that when properly configured, system hook 305 can governnearly any function or property within nearly any media playerapplication that may be operational within a client computer system,e.g., 210-230. In one embodiment, system hook 305 is a DLL (dynamic linklibrary) file. It is further noted that system hooks are well known inthe art, and are a standard facility in a Microsoft Windows™ operatingenvironment, and accordingly can be implemented in a variety of ways.However, it is also noted that system hook 305 can be readily adaptedfor implementation in alternative operating systems, e.g., Apple™operating systems, Sun Solaris™ operating systems, Linux operatingsystems, and nearly any other operating system.

In FIG. 3, copyright compliance mechanism 300 also includes one or moreskins 306, which can be designed to be installed in a client computersystem, e.g., 210-230. In one embodiment, skins 306 are utilized toassist in client side compliance with the DMCA (digital millenniumcopyright act) regarding copyrighted media content. Skins 306 arecustomizable interfaces that, in one embodiment, are displayed on adisplay device (e.g., 105) of computer system 210 and providefunctionalities for user interaction of delivered media content.Additionally, skins 306 can also provide a display of informationrelative to the media content file including, but not limited to, songtitle, artist name, album title, artist bio, and other features such aspurchase inquiries, advertising, and the like.

Furthermore, when system hook 305 is unable to govern a function of themedia player application operable on a client computer system, e.g.,210, such that client computer system could be in non-compliance withDMCA and/or RIAA restrictions, a skin 306 can be implemented to providecompliance.

Differing skins 306 can be implemented depending upon the DMCA and/orRIAA restrictions applicable to each media content file. For example, inone embodiment, a skin 306 a may be configured for utilization with amedia content file protected under a non-interactive agreement (DMCA),such that skin 306 a may not include a pause function, a stop function,a selector function, and/or a save function, etc. Another skin, e.g.,skin 306 b may, in one embodiment, be configured to be utilized with amedia content file protected under an interactive with “no save”agreement (DMCA), such that skin 306 b may include a pause function, astop function, a selector function, and for those media files having aninteractive with “save” agreement, a save or a burn to CD function.

Still referring to FIG. 3, it is further noted that in the presentembodiment, each skin 306 can have a unique name and signature. In oneembodiment, skin 306 can implemented, in part, through the utilizationof an MD (message digest) 5 hash table or similar algorithm. An MD5 hashtable can, in one implementation, be a check-sum algorithm. It is wellknown in the art that a skin, e.g., skin 306, can be renamed and/ormodified to incorporate additional features and/or functionalities in anunauthorized manner. Since modification of the skin would change thecheck sum and/or MD5 hash, without knowledge of the MD5 hash table,changing the name or modification of the skin may simply serve todisable the skin, in accordance with one embodiment of the presentinvention. Since copyright compliance mechanism 300 verifies skin 306,MD5 hash tables advantageously provide a deterrent against modificationsmade to the skin.

In one embodiment, copyright compliance mechanism 300 also includes oneor more custom media device driver(s) 307 for providing an even greatermeasure of control over the media stream while increasing compliancereliability. A client computer system, e.g., 210, can be configured toutilize a custom media device application, e.g., custom media device 310(shown in FIGS. 5B, 5C, and 5D), to control unauthorized recording ofmedia content files. A custom media device application can be, but isnot limited to, a custom media audio device application for media fileshaving sound content, a custom video device application for media fileshaving graphical and/or alphanumeric content, etc. In one embodiment,custom media device 310 of FIG. 5B is an emulation of the custom mediadevice driver 307. With reference to audio media, the emulation isperformed in a waveform audio driver associated with custom media device310. Driver 307 is configured to receive a media file being outputted bysystem 210 prior to the media file being sent to a media output device,e.g., media output device 570, and/or a media output application, e.g.,recording application 502. Examples of a media output device includes,but is not limited to, a video card for video files, a sound card foraudio files, etc. Examples of a recording application can include, butis not limited to, CD burner applications for writing to another CDs,ripper applications which capture the media file and change the formatof the media file, e.g., from a CD audio file to an .mpeg audio file,and/or a .wav file, and/or an ogg vorbis file, and various other mediaformats. In one embodiment, client computer system 210 is configuredwith a custom media device driver 307 emulating custom media device 310,and which is system 210's default device driver for media file output.In one embodiment, an existing GUI (graphical user interface) can beutilized or a GUI can be provided, e.g., by utilization of skin 306 or acustom web based player application or as part of a CCM 300 installationbundle, for forcing or requiring system 210 to have driver 307 as thedefault driver.

Therefore, when a media content file is received by system 210 fromserver 251, the media content file is playable, provided the mediacontent file passes through the custom media device application (e.g.,310 of FIG. 5B), emulated by custom media device driver 307, prior tobeing outputted. However, if an alternative media player application isselected, delivered media files from server 251 will not play on system210.

Thus, secured media player applications would issue a media request tothe driver, e.g., 307, for the custom media device 310 which thenperforms necessary media input suppression, e.g., waveform suppressionfor audio files, prior to forwarding the request to the default Windows™media driver, e.g., waveform audio driver for audio files.

It is noted that requests for non-restricted media files can passdirectly through custom media device driver 307 to a Windows™ waveformaudio driver operable on system 210, thus reducing instances ofincompatibilities with existing media player applications that utilizewaveform media, e.g., audio, video, etc. Additionally, media playerapplications that do not support secured media would be unaffected. Itis further noted that for either secured media or non-restricted media,e.g., audio media files, waveform input suppression can be triggered byother components of CCM 300, e.g., agents 304, system hooks 305, andskins 306, or a combination thereof, to be active when a recordingoperation is initiated simultaneously with playback of secured mediafiles, e.g., audio files. Custom device drivers are well known and canbe coded and implemented in a variety of ways including, but limited to,those found at developers network web sites, e.g., a Microsoft™ oralternative OS (operating system) developer web sites.

Advantageously, by virtue of system 210 being configured with a custommedia device as the default device driver e.g., device 310 of FIGS. 5B,5C, and 5D, emulated by a custom media device driver 307, those mediaplayer applications that require their particular device driver to bethe default driver, e.g., Total Recorder, etc., are renderednon-functional for secured music. Further advantageous is that anemulated custom media device provides no native support for those mediaplayer applications used as a recording mechanism, e.g., DirectSoundcapture, (direct sound 504 of FIGS. 5A, 5B, 5C, and 5D) etc., that areable to bypass user-mode drivers for most media devices. Additionally,by virtue of the media content being sent through device driver 307,thus effectively disabling unauthorized saving/recording of media files,in one embodiment, media files that are delivered in a secured deliverysystem do not have to be encrypted, although, in another embodiment,they still may be encrypted. By virtue of non-encrypted media filesutilizing less storage space and network resources than encrypted mediafiles, networks having limited resources can utilize the functionalitiesof driver 307 of CCM 300 to provide compliance with copyrightrestrictions and/or licensing agreements applicable with a media contentfile without having the processing overhead of encrypted media files.

FIG. 4 is an illustration of an exemplary system 400 for implementing acopyright compliance mechanism in accordance with an embodiment of thepresent invention. Specifically, system 400 illustrates web server 250,content server 251, or a combination of web server 250 and contentserver 251 installing a copyright compliance mechanism (e.g., 300) in aclient's computer system (e.g., 210) for controlling media filedistribution and controlling user access and interaction of copyrightedmedia files, in one embodiment of the present invention.

Client computer system 210 can communicatively couple with a network(e.g., 200) to request a media file, a list of available media files, ora play list of audio files, e.g., MP3 files, etc. In response, webserver 250 determines if the request originates from a registered userauthorized to receive media files associated with the request. If theuser is not registered with the network, web server 250 can initiate aregistration process with the requesting client 210. Client registrationcan be accomplished in a variety of ways. For example, web server 250may deliver to a client 210 a registration form having various textentry fields into which the user can enter required information. Avariety of information can be required from the user by web server 250including, but not limited to, user's name, address, phone number,credit card number, online payment account number, biometricidentification (e.g., fingerprint, retinal scan, etc.), verifiable emailaddress, and the like. In addition, registration can, in one embodiment,include a requirement for the user to select a username and password.

Still referring to FIG. 4, web server 250 can, in one embodiment, detectinformation related to the client's computer system, e.g., 210, andstore that information in a user/media database 450. For example, webserver 250 can detect a unique identifier of client computer system 210.In one embodiment, the unique identifier can be the MAC (machine addresscode) address of a NIC (network interface card) of client computersystem 210 or the MAC address of the network interface adapterintegrated on the motherboard of system 210. It is understood that a NICenables a client computer system 210 to access web server 250 viaInternet 201. It is well known that each NIC typically has a uniqueidentifying number MAC address. Further, web server 250 can, in oneembodiment, detect and store (also in database 450) informationregarding the types(s) of media player application(s), e.g., WindowsMedia Player™, Real Player™, iTunes player™ (Apple), Live 365™ player,and those media player applications having recording functionality,e.g., Total Recorder, Cool Edit 2000, Sound Forge, Sound Recorder, SuperMP3 Recorder, and the like, that are present and operable in clientcomputer system 210. In one embodiment, the client information isverified for accuracy and is then stored in a user database (e.g., 450)within web server 250.

Subsequent to registration completion, creation of the user ID andpassword, and obtaining information regarding client computer system210, all or part of this information can be installed in client computersystem 210. In one embodiment, client computer system 210 informationcan be in the form of a cookie. Web server 250 then verifies that theuser and client computer system 210 data is properly installed thereinand that their integrity has not been compromised. Subsequently, webserver 250 installs a copyright compliance mechanism (e.g., 300) intothe client's computer system, e.g., 210, in one embodiment of thepresent invention. It is noted that web server 250 may not initiateinstallation of CCM 300 until the user ID, password, and client computersystem 210 information is verified. A variety of common techniques canbe employed to install an entire CCM 300, portions of components, entirecomponents, and/or combinations or a function of components. Forexample, copyright compliance mechanism 300 can be installed in a hiddendirectory within client computer system 210, thereby preventingunauthorized access to it. In one embodiment of the present invention,it is noted that unless CCM 300 is installed in client computer system210, its user will not be able to request, access, or have deliveredthereto, media files stored by web server 250 and/or content server 251.

Referring still to FIG. 4, upon completion of client registration andinstallation of CCM 300, client computer system 210 can then request amedia play list or a plurality of play lists, etc. In response, webserver 250 determines whether the user of client computer system 210 isauthorized to receive the media play list associated with the request.In one embodiment, web server 250 can request the username and password.Alternatively, web server 250 can utilize user database 450 to verifythat computer 210 is authorized to receive a media play list. If clientcomputer 210 is not authorized, web server 250 can initiate clientregistration, as described herein. Additionally, web server 250 candisconnect computer 210 or redirect it to an alternative web site.Regardless, if the user and client computer system 210 are notauthorized, web server 250 will not provide the requested play list toclient computer system 210.

However, if client computer system 210 is authorized, web server 210 cancheck copyright compliance mechanism 300 within data base 450 todetermine if it, or any of the components therein, have been updatedsince the last time client computer system 210 logged in to web server250. If a component of CCM 300 has been updated, web server 250 caninstall the updated component and/or a more current version of CCM 300into client computer system 210, e.g., via Internet 201. If CCM 300 hasnot been updated, web server 250 can then deliver the requested mediaplay list to system 210 via Internet 201 along with an appended user keyor user identification (ID). It is noted that user database 450 can alsoinclude data for one or more media play lists that can be utilized toprovide a media play list to client computer system 210. Subsequently,the user of client computer system 210 can utilize the received mediaplay list in combination with the media player application operating onsystem 210 to transmit a delivery request for one or more desired piecesof media content from web server 250. It is noted that the deliveryrequest contains the user key for validation purposes.

Still referring to FIG. 4, upon receiving the media content deliveryrequest, web server 250 can then check the validity of the requestingmedia application and the attached user key. In one embodiment, webserver 250 can utilize user database 450 to check their validity. Ifeither or both are invalid, web server 250, in one embodiment, canredirect unauthorized client computer system 210 to an alternativedestination to prevent abuse of the system. However, if both therequesting media application and the user key are valid, CCM 300verifies that skins 306 are installed in client computer system 210.Additionally, CCM 300 further verifies that system hook(s) 305 have beenrun or are running to govern certain functions of those media playerapplications operable within client computer system 210 that are knownto provide non-compliance with the DMCA and/or the RIAA. Additionally,CCM 300 further diverts and/or redirects certain pathways that arecommonly used for recording, e.g., driver 307 of FIG. 5A, device 310 ofFIG. 5B, device 570 of FIG. 5C, and driver 505 of FIG. 5D. Once CCM 300has performed the above described functions, web server 250 then, in oneembodiment, issues to the client computer 210 a redirect command to thecurrent address location of the desired media file content along with anoptional time sensitive access key, e.g., for that hour, day, or otherdefined timeframe.

In response to the client computer system 210 receiving the redirectcommand from web server 250, the media player application operating onclient computer system 210 automatically transmits a new request and thetime sensitive access key to content server 251 for delivery of one ormore desired pieces of media content. The validity of the time sensitiveaccess key is checked by content server 251. If invalid, unauthorizedclient computer 210 is redirected by content server 250 to protectagainst abuse of the system and unauthorized access to content server251. If the time sensitive access key is valid, content server 251retrieves the desired media content from content database 451 anddelivers it to client computer system 210. It is noted that, in oneembodiment, the delivered media content can be stored in hiddendirectories and/or custom file systems that may be hidden within clientcomputer system 210 thereby preventing future unauthorized distribution.In one embodiment, an HTTP (hypertext transfer protocol) file deliverysystem is used to deliver the requested media files, meaning that themedia files are delivered in their entirety to client computer system210, as compared to streaming media which delivers small portions of themedia file.

Still referring to FIG. 4, it is noted that each media file has, in oneembodiment, had a header attached therewith prior to delivery of themedia file. In one embodiment, the header can contain informationrelating to the media file, e.g., title or media ID, media data such assize, type of data, and the like. The header can also contain a sequenceor key that is recognizable to copyright compliance mechanism 300 thatidentifies the media file as originating from a content server 251. Inone embodiment, the header sequence/key can also contain instructionsfor invoking the licensing agreements and/or copyright restrictions thatare applicable to that particular media file.

Additionally, if licensing agreements or copyright restrictions arechanged, developed, or created, or if new media player applications,with or without recording functionality, are developed, CCM 300 wouldhave appropriate modifications made to portions of components, entirecomponents, combinations of components, and/or the entire CCM 300 toenable continued compliance with licensing agreements and copyrightrestrictions. Furthermore, subsequent to modification of copyrightcompliance mechanism 300, modified portions of, or the entire updatedCCM 300 can easily be installed in client computer system 210 in avariety of ways. For example, the updated CCM 300 can be installedduring client interaction with web server 250, during user log-in,and/or while client computer system 210 is receiving the keyed playlist.

Referring still to FIG. 4, it is further noted that, in one embodiment,the media files and attached headers can be encrypted prior to beingstored within content server 251. In one embodiment, the media files canbe encrypted utilizing randomly generated keys. Alternatively, variablelength keys can be utilized for encryption. It is noted that the key todecrypt the encrypted media files can be stored in a database 450,content database 451 or in some combination of databases 450 and 451. Itis further noted that the messages being passed back and forth betweenclient computer system 210 and web server 250 can also be encrypted,thereby protecting the media files and the data being exchanged fromunauthorized use or access. There are a variety of encryption mechanismsand programs that can be implemented to encrypt this data including, butnot limited to, exclusive OR, shifting with adds, public domainencryption programs such as Blowfish, and non-public domain encryptionmechanisms. It is also noted that each media file can be uniquelyencrypted, such that if the encryption code is cracked for one mediafile, it is not applicable to other media files. Alternatively, groupsof media files can be similarly encrypted. Furthermore, in anotherembodiment, the media files may not be encrypted when being delivered toa webcaster known to utilize a proprietary media player application,e.g., custom media device driver 307.

Subsequent to media file decryption, the media file may be passedthrough CCM 300, e.g., a coder/decoder 303, to a media playerapplication operating on client computer system 210, e.g. playbackapplication 501 of FIGS. 5A, 5B, 5C, 5D, and 6A, which can then accessand utilize the delivered high fidelity media content, enabling itsuser(s) to experience the media content, e.g., listen to it, watch it,view it, or the like. In one embodiment of the present invention, aspecialized or custom media player may or may not be required toexperience the media content, e.g., skin 306 of FIG. 3. A skin 306 maybe necessary when CCM 300 cannot modify an industry standard mediaplayer application to comply with copyright restrictions and/orlicensing agreements in accordance with the DMCA. Alternatively, anindustry standard media player can be utilized by client computer system2 10 to experience the media content. Typically, many media playerapplications are available and can include, but are not limited to,Windows™ Media Player™ for PCs (personal computers), iTunes™ Player orQuickTime™ for Apple computers, and XMMS player for computers utilizinga Linux operating system. Regardless of the media player applicationutilized, while the media file is passed to the media playerapplication, e.g., in a frame by frame basis or in a buffer,coder/decoder 303 will repeatedly ensure that CCM 300 rules are beingenforced at any particular moment during media playback, shown as step650 of FIG. 6C.

As the media file content is delivered to the media player application,periodically, e.g., after a specified number of frames, after a definedperiod of time, or any desired time or data period, coder/decoder 303repeatedly determines whether or not all the rules are enforced, inaccordance with rules as defined by CCM 300. If the rules are notenforced, e.g., change due to a user opening up a recording application,e.g., Total Recorder or alternative application, the presentation of themedia content is, in one embodiment, suspended or halted. In anotherembodiment, the presentation of the media content can be modified tooutput the media content non audibly, e.g., silence. In yet anotherembodiment, the media content may be audible but recording functionalitycan be disabled, such that the media content cannot be recorded. Thesepresentation stoppages are collectively shown as step 651 of FIG. 6C.

If the rules, in accordance with CCM 300, are enforced, thecodec/decoder 303 retrieves a subsequent portion of the media contentthat is stored locally in client computer system 210. The newlyretrieved portion of the media file is then presented by the client'smedia player application. While the newly retrieved portion ispresented, CCM 300 then again checks that the rules are enforced, andretrieves an additional portion of the media file or suspendspresentation of the media file is the rules are not being enforced, andthese steps are performed repeatedly throughout the playback of themedia file, in a loop environment, until the media file's contents havebeen presented in their entirety. Advantageously, by constant monitoringduring playing of media files, CCM 300 can detect undesired activitiesand enforces those rules as defined by CCM 300.

FIG. 5A is an exemplary logic/bit path block diagram 500A showingutilization of a wave shim driver, e.g., wave shim driver 309 of FIG. 3,in conjunction with copyright compliance mechanism 300, for selectivelycontrolling recording of copyrighted media received by a client computersystem, e.g., system 210, in one embodiment of the present invention.Copyright compliance mechanism 300 is, in one embodiment, installed andoperational on client system 210 in the manner described herein.

In one embodiment, a copyright compliance mechanism 300 is shown asbeing communicatively coupled with a media playback application 501 viaconnection 520. Therefore, CCM 300 is enabled to communicate withplayback application 501. In one embodiment, CCM 300 can be integratedinto a media playback application. CCM 300 is also coupled to andcontrols a selectable switch 311 in wave shim driver 309 (as describedin FIG. 3) via connection 522. CCM 300 is further coupled to andcontrols a selectable switch 511 in direct sound 504 via connection 521.Depending upon the copyright restrictions and licensing agreementsapplicable to an incoming media file, e.g., 499, CCM 300 controlswhether switches 311 and 511 are open (shown), thus preventing incomingmedia 499 from reaching a media recording application, or closed (notshown) to allow recording of incoming media 499.

For example, incoming media 499 may originate from a content server,e.g., 251, coupled to system 210. In another example, incoming media 499may originate from a personal recording/electronic device, e.g., a MP3player/recorder or similar device, coupled to system 210. Alternatively,incoming media 499 may originate from a magnetic, optical or alternativemedia storage device inserted into a media device player coupled tosystem 210, e.g., a CD or DVD inserted into a CD or DVD player, a harddisk in a hot swappable hard drive, an SD (secure digital card) insertedinto a SD reader, and the like. In yet another example, incoming media499 may originate from another media player application or mediarecording application. Incoming media 499 may also originate from asatellite radio feed (e.g., XM radio), a personal communication device(e.g., a mobile phone), a cable television radio input (e.g., DMX(digital music express)), a digital distribution and/or a publicpresentation source via a network, Internet or other communicationconnection, pay-per-view and/or pay-per-play system, or a set-top box.It is noted that incoming media 499 can originate from nearly any sourcethat can be coupled to system 210. However, regardless of the source ofincoming media 499, embodiments of the present invention, describedherein, can prevent unauthorized recording of the media.

FIG. 5A shows a media playback application 501, e.g., an audio, video,or other media player application, operable within system 210 andconfigured to receive incoming media 499. Playback application 501 canbe a playback application provided by an operating system, e.g., MediaPlayer for Windows™ by Microsoft, a freely distributed playbackapplication downloadable from the Internet, e.g., RealPlayer orLiquidAudio, a playback application provided by a webcaster, e.g.,PressPlay, or a playback application commercially available.

FIG. 5A shows media device driver 505 which, in one implementation, maybe a software driver for a sound card coupled to system 210 having amedia output device 570, e.g., speakers or headphones, coupled therewithfor media files having audio content. In another implementation, mediadevice driver 505 may be a software driver for a video card coupled witha display device, e.g., 105, for displaying media files havingalphanumeric and/or graphical content, and so on. With reference toaudio files, it is well known that a majority of recording applicationsassume a computer system, e.g., 210, has a sound card disposed therein,providing full-duplex sound functionality to system 210. This meansmedia output driver 505 can simultaneously cause playback and recordingof incoming media files 499. For example, media device driver 505 canplayback media 499 along wave-out line 539 to media output device 570(e.g., speakers for audible playback) via wave-out line 580 whileoutputting media 499 on wave-out line 540 to eventually reach recordingapplication 502.

For purposes of FIGS. 5A, 5B, 5C, and 5D, the terms wave-in line andwave-out line are referenced from the perspective of media device driver505. Additionally, for the most part, wave-in lines are downwardlydepicted and wave-out lines are upwardly depicted in FIGS. 5A, 5B, 5C,and 5D.

Continuing with FIG. 5A, playback application 501 is coupled with anoperating system (O/S) multimedia subsystem 503 and direct sound 504 viawave-in lines 531 and 551 respectively. O/S multimedia subsystem 503 iscoupled to a wave shim driver 309 via wave-in line 533 and wave-out line546. O/S multimedia subsystem 503 is also coupled to a recordingapplication 502 via wave-out line 548. Operating system (O/S) multimediasubsystem 503 can be any O/S multimedia subsystem, e.g., a Windows™multimedia subsystem for system 210 operating under a Microsoft O/S, aQuickTime™ multimedia subsystem for system 210 operating under an AppleO/S, and so on. Playback application 501 is also coupled with directsound 504 via wave-in line 551.

Direct sound 504, in one instance, may represent access to a hardwareacceleration feature in a standard audio device, enabling lower levelaccess to components within media device driver 505. In anotherinstance, direct sound 504 may represent a path that can be used by arecording application, e.g., Total Recorder, that can be furtherconfigured to bypass the default device driver, e.g., media devicedriver 505 to capture incoming media 499 for recording. For example,direct sound 504 can be enabled to capture incoming media 499 viawave-in line 551 and unlawfully output media 499 to a recordingapplication 502 via wave-out line 568, as well as media 499 eventuallygoing to media device driver 505, the standard default driver.

Still referring to FIG. 5A, wave shim driver 309 is coupled with mediadevice driver 505 via wave-in line 537 and wave-out line 542. Mediadevice driver 505 is coupled with direct sound 504 via wave-in line 553which is shown to converge with wave-in line 537 at media device driver505. Media device driver 505 is also coupled with direct sound 504 viawave-out line 566.

Wave-out lines 542 and 566 are shown to diverge from wave-out line 540at media device driver 505 into separate paths. Wave-out line 542 feedsinto wave shim driver 309 and wave-out line 566 feeds into direct sound504. When selectable switch 311 and 511 are open (shown), incoming media499 cannot flow to recording application 502, thus preventingunauthorized recording of it.

For example, incoming media 499 is received at playback application 501.Playback application 501 activates and communicates to CCM 300 regardingcopyright restrictions and/or licensing agreements applicable toincoming media 499. If recording restrictions apply to media 499, CCM300 can, in one embodiment, open switches 311 and 511, thereby blockingaccess to recording application 502, effectively preventing unauthorizedrecording of media 499. In one embodiment, CCM 300 can detect if system210 is configured with direct sound 504 selected as the default driverto capture incoming media 499, via wave-in line 551, or a recordingapplication is detected and/or a hardware accelerator is active, suchthat wave driver shim 309 can be bypassed by direct sound 504. Upondetection, CCM 300 can control switch 511 such that the output path,wave-out line 568, to recording application 502 is blocked. It isfurther noted that CCM 300 can detect media recording applications anddevices as described herein, with reference to FIG. 3.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 is output from playback application 501 toO/S multimedia subsystem 503 on wave-in line 531. From subsystem 503,media 499 is output to wave shim driver 309 via wave-in line 533. Thewave shim driver 309 was described herein with reference to FIG. 3.Media 499 is output from wave shim driver 309 to media device driver 505via wave-in line 537. Once received by media device driver 505, media499 can be output via wave-out line 539 to a media output device 570coupled therewith via wave-out line 580. Additionally, media devicedriver 505 can simultaneously output media 499 on wave-out line 540 backto wave shim driver 309. Dependent upon recording restrictionsapplicable to media 499, CCM 300 can, in one embodiment, close switch311 (not shown as closed), thereby allowing media 499 to be output fromwave shim driver 309 to subsystem 503 (via wave-out line 546) and thento recording application 502 via wave-out line 548. Alternatively, CCM300 can also open switch 311, thereby preventing media 499 from reachingrecording application 502.

It is particularly noted that by virtue of CCM 300 controlling bothswitches 311 and 511, and therefore controlling wave-out line 548 andwave-out line 568 leading into recording application 502, incoming mediafiles, e.g., media 499, can be prevented from being recorded in anunauthorized manner in accordance with applicable copyright restrictionsand/or licensing agreements related to the incoming media. It is alsonoted that embodiments of the present invention in no way interfere withor inhibit the playback of incoming media 499.

FIG. 5B is an exemplary logic/bit path block diagram 500B of a clientcomputer system, e.g., 210, configured with a copyright compliancemechanism 300 for preventing unauthorized recording of copyrighted mediaaccording to an embodiment of the present invention. Copyrightcompliance mechanism 300 is, in one embodiment, coupled with andoperational on client system 210 in the manner with reference to FIGS.4, 5A, 5C, 5D, 6, and 7.

Diagram 500B of FIG. 5B is similar to diagram 500A of FIG. 5A, with afew changes. Particularly, diagram 500B includes a custom media device310 communicatively interposed between and coupled to O/S multimediasubsystem 503 and wave shim driver 309. Custom media device 310 iscoupled to O/S multimedia subsystem via wave-in line 533 and wave-outline 546. Custom media device 310 is coupled with wave shim driver 309via wave-in line 535 and wave-out line 544. Additionally, custom mediadevice 310 is coupled with direct sound 504 via wave-in line 553 whichconverges with wave-in line 533 and wave-out line 566 which divergesfrom wave-out line 546, in one embodiment.

Also added to FIG. 5B is a media hardware output device 570 that iscoupled to media device hardware driver 505 via line 580. Media hardwareoutput device 570 can be, but is not limited to, a sound card for audioplayback, a video card for video, graphical, alphanumeric, etc, output,and the like.

In one embodiment, CCM 300 is communicatively coupled with playbackapplication 501 via connection 520, waveform driver shim 309 viaconnection 522, and custom media device 310, via connection 521. CCM 300is coupled to and controls a selectable switch 311 in waveform drivershim 309 via connection 522. CCM 300 is also coupled to and controls aselectable switch 312 in custom audio device 310 via connection 521.Depending upon the copyright restrictions and licensing agreementsapplicable to an incoming media file, e.g., media 499, CCM 300 controlswhether switches 311 and 312 are open (shown), thus preventing theincoming media 499 from reaching a recording application, or closed (notshown) so as to allow recording of the incoming media 499.

Continuing with FIG. 5B, direct sound 504 is shown coupled with custommedia device 310 via wave-in line 553, instead of being coupled withmedia device driver 505 (FIG. 5A). In one embodiment, custom audiodevice 310 mandates explicit selection through system 210, meaning thatcustom audio device 310 needs to be selected as a default driver ofsystem 210. By virtue of having the selection of custom media device 310as the default driver of system 210, the data path necessary for directsound 504 to capture the media content is selectively closed.

For example, incoming media 499 originating from nearly any source withreference to FIG. 5A is received by media playback application 501 ofsystem 210. Playback application 501 communicates to CCM 300, viaconnection 520, to determine whether incoming media 499 is protected byany copyright restrictions and/or licensing agreements. Playbackapplication 501 communicates with CCM 300 to control switch 311 and 312accordingly. In the present example, recording of incoming media 499would violate applicable restrictions and/or agreements and thereforeswitch 312 is in an open position, such that the output path torecording application 502, e.g., wave-out line 548 and/or wave-out line568, is effectively blocked, thereby preventing unauthorized recordingof media 499.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 continues from O/S multimedia subsystem 503,through custom audio device 310, wave driver shim 309, and into mediadevice driver 505 where media 499 can be simultaneously output to mediaoutput device 570 via line 580, and output on wave-out line 540 towave-and outputted by media device driver 505 to wave shim driver 309 onwave-out line 542. However, by virtue of CCM 300 controlling switch 311,wave-out line 544 which eventually leads to recording application 502 isblocked, thus effectively preventing unauthorized recording of media499.

It is particularly noted that by virtue of CCM 300 controlling bothswitches 311 and 312 and therefore controlling wave-out line 548 andwave-out line 568, any incoming media files, e.g., incoming media 499,can be prevented from being recording in an unauthorized manner inaccordance with applicable copyright restrictions and/or licensingagreements related to the incoming media.

Still referring to FIG. 5B, it is further noted that custom media device310 allows for unfettered playback of incoming media 499. Additionally,at any time during playback of media 499, custom media device 310 can bedynamically activated by CCM 300.

FIG. 5C is an exemplary logic/bit path block diagram 500C of a clientcomputer system, e.g., 210, configured with a copyright compliancemechanism 300 for preventing unauthorized output and unauthorizedrecording of copyrighted media according to an embodiment of the presentinvention. Copyright compliance mechanism 300 is, in one embodiment,coupled with and operational on client system 210 in the manner withreference to FIGS. 4, 5A, 5B, 5D, 6, and 7.

Diagram 500C of FIG. 5C is similar to diagram 500B of FIG. 5B, with afew changes. Particularly, diagram 500C includes a media hardware outputdevice 570 that is coupled with a media device driver 505. In oneembodiment, media hardware output device 570 can be a S/PDIF(Sony/Phillips Digital Interface) card for providing multiple outputs,e.g., an analog output 573 and a digital output 575. An alternativemedia hardware output device providing similar digital output can alsobe implemented as device 570 including, but not limited to, a USB(universal serial bus) output device and/or an externally accessible USBport located on system 210, a FireWire (IEEE1394) output device and/oran externally accessible FireWire port located on system 210, withwireline or wireless functionality. In the present embodiment, mediahardware output device 570 is shown to include a switch 571 controlledby CCM 300 via communication line 523, similar to switches 311 and 312,for controlling output of incoming media 499.

In one embodiment, CCM 300 is communicatively coupled with playbackapplication 501 via connection 520, waveform driver shim 309 viaconnection 522, custom media device 310, via connection 521, and mediahardware output device 570 via connection 523. CCM 300 is coupled to andcontrols a selectable switch 311 in waveform driver shim 309 viaconnection 522. CCM 300 is also coupled to and controls a selectableswitch 312 in custom audio device 310 via connection 521. CCM 300 isfurther coupled to and controls a selectable switch 571 in mediahardware output device 570 via connection 523. Depending upon thecopyright restrictions and licensing agreements applicable to anincoming media file, e.g., media 499, CCM 300 controls whether switches311 and 312 are open (shown), thus preventing the incoming media 499from reaching a recording application, or closed (not shown) so as toallow recording of the incoming media 499. Additionally, CCM 300controls whether switch 571 is open (shown), thus preventing incomingmedia 499 from being output from digital output 575 of media hardwareoutput device 570, or closed (not shown) to allow incoming media 499 tobe output from media hardware output device 570.

By controlling media hardware output device 570, copyright compliancemechanism 300 can prevent unauthorized output of incoming media 499 to,e.g., a digital recording device that may be coupled with digital output575 of media hardware output device 570. Accordingly, in one embodiment,CCM 300 is enabled to also detect digital recording devices that may becoupled to a digital output line, e.g., 571, of a media hardware outputdevice, e.g., 570. Examples of a digital recording device that can becoupled to media hardware output device 570 can include, but is notlimited to, mini-disc recorders, MP3 recorders, personal digitalrecorders, digital recording devices coupled with multimedia systems,personal communication devices, set-top boxes, and/or nearly any digitaldevice that can capture an incoming media 499 being output from a mediahardware output device 570, e.g., a sound card.

Continuing with FIG. 5C, direct sound 504 is shown coupled with custommedia device 310 via wave-in line 553, instead of being coupled withmedia device driver 505 (FIG. 5A). In one embodiment, custom audiodevice 310 mandates explicit selection through system 210, meaning thatcustom audio device 310 is needs to be selected as a default driver ofsystem 210. By virtue of having the selection of custom media device 310as the default driver of system 210, the data path necessary for directsound 504 to capture the media content is selectively closed.

For example, incoming media 499 originating from nearly any source withreference to FIG. 5A is received by media playback application 501 ofsystem 210. Playback application 501 communicates to CCM 300, viaconnection 520, to determine whether incoming media 499 is protected byany copyright restrictions and/or licensing agreements. Playbackapplication 501 communicates with CCM 300 to control switch 311, 312,and 571 accordingly. In the present example, recording of incoming media499 would violate applicable restrictions and/or agreements andtherefore switch 312 is in an open position, such that the output pathto recording application 502, e.g., wave-out line 548 and/or wave-outline 568, is effectively blocked, thereby preventing unauthorizedrecording of media 499.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 continues from O/S multimedia subsystem 503,through custom audio device 310, wave driver shim 309, and into mediadevice driver 505 where media 499 can be simultaneously output to mediaoutput device 570 via line 580, and output on wave-out line 540 towave-and outputted by media device driver 505 to wave shim driver 309 onwave-out line 542. However, by virtue of CCM 300 controlling switch 311,wave-out line 544 which eventually leads to recording application 502 isblocked, thus effectively preventing unauthorized recording of media499.

It is particularly noted that by virtue of CCM 300 controlling bothswitches 311 and 312 and therefore controlling wave-out line 548 andwave-out line 568, any incoming media files, e.g., incoming media 499,can be prevented from being recording in an unauthorized manner inaccordance with applicable copyright restrictions and/or licensingagreements related to the incoming media.

Still referring to FIG. 5C, it is particularly noted that although CCM300 can prevent unauthorized recording of incoming media 499 bycontrolling switches 311 and 312, thus preventing incoming media 499from reaching recording application 502, controlling switches 311 and312 do nothing to prevent incoming media 499 from being captured by aperipheral digital device, e.g., a mini-disc recorder, etc., coupled toa digital output 575 of device 570. Thus, by also controlling theoutput, via digital output 575 of media hardware output device 570,through control of switch 571, CCM 300 can prevent unauthorizedcapturing of incoming media 499 during output, e.g., on a sound card foraudio files, a video card for video and/or graphical files, regardlessof whether incoming media 499 is received in a secure and encryptedmanner. However, when switch 571 is in a closed position, incoming media499 may be played back in an unfettered manner. Additionally, at anytime during playback of media 499, switch 312 of custom media device310, switch 311 of media device driver 309, and/or switch 571 of mediahardware output device 570 can be dynamically activated by CCM 300.

FIG. 5D is an exemplary logic/bit path block diagram 500D of a clientcomputer system, e.g., 210, configured with a copyright compliancemechanism 300 for preventing unauthorized kernel based output andunauthorized recording of copyrighted media according to an embodimentof the present invention. Copyright compliance mechanism 300 is, in oneembodiment, coupled with and operational on client system 210 in themanner described herein with reference to FIGS. 4, 5A, 5B, 5C, 6, and 7.

Diagram 500D of FIG. 5D is similar to diagram 500C of FIG. 5C, with somechanges. Particularly, diagram 500D includes a kernel streamingmechanism 515, e.g., DirectKS, that is coupled with a media devicedriver 505. In one embodiment, DirectKS 515 can be used for establishinga direct connection with media device driver 505. In the presentembodiment, media device driver 505 is shown to include a switch 511controlled by CCM 300 via communication line 524, that is similar toswitches 311, 312, and 571, for controlling output of incoming media499.

In one embodiment, CCM 300 is communicatively coupled with: playbackapplication 501 via connection 520, waveform driver shim 309 viaconnection 522, custom media device 310, via connection 521, and mediadevice driver 5O via connection 524. Specifically, CCM 300 is coupled toand controls a selectable switch 311 in waveform driver shim 309 viaconnection 522. CCM 300 is also coupled to and controls a selectableswitch 312 in custom audio device 310 via connection 521. CCM 300 isfurther coupled to and controls a selectable switch 511 in media devicedriver 505 via connection 524. Depending upon the copyright restrictionsand licensing agreements applicable to an incoming media file, e.g.,media 499, CCM 300 controls whether switches 311 and 312 are open(shown), thus preventing the incoming media 499 from reaching arecording application, or closed (not shown) so as to allow recording ofthe incoming media 499. Additionally, CCM 300 controls whether switch511 is open (shown), thus preventing incoming media 499 from beingreturned from media device driver 505 to playback application 501, whereDirectKS 515 can capture incoming media 499 and redirect it to recordingapplication 502 to create an unauthorized copy or recording of incomingmedia 499. CCM 300 can also control whether switch 511 is closed (notshown) to allow incoming media 499 to be returned to playbackapplication 501, where DirectKS 515 can capture and redirect incomingmedia 499 to recording application 502.

DirectKS 515, in one embodiment, may represent a kernel streamingmechanism that is adapted to establish a direct connection with a mediadevice driver 505 of an operating system operable on client computersystem 210, enabling kernel level access to media device driver 505. Akernel streaming mechanism can be implemented for the purpose ofprecluding utilization of standard audio APIs (application programminginterfaces) to play or record media content, with particular attentionpaid to those playback applications with low latency requirements.DirectKS 515 can bypass existing APIs and communicate with media devicedriver 505. DirectKS 515 can be readily adapted to work in conjunctionwith a playback application, e.g., 501, to capture and redirect incomingmedia 499 to recording application 502, via wave-out line 588.Accordingly, DirectKS 515 can be implemented to create unauthorizedmedia recordings.

By controlling media device driver 505, copyright compliance mechanism300 can prevent unauthorized output of incoming media 499 to, e.g., adigital recording device 529 that may be coupled with recordingapplication 502. In one embodiment, media device driver 505 isconfigured through the kernel mixer (not shown) to control the datapath. Additionally, in one embodiment, CCM 300 is enabled to also detecta kernel streaming mechanism 515 (e.g., DirectKS) that may be operableon client computer system 210, as described herein with reference toFIG. 3.

In one embodiment, custom media device 310 mandates explicit selectionthrough system 210, meaning that custom media device 310 is needs to beselected as a default driver of system 210. By virtue of having theselection of custom media device 310 as the default driver of system210, the data path necessary for direct sound 504 to capture the mediacontent is selectively closed.

For example, incoming media 499 originating from nearly any source withreference to FIG. 5A is received by media playback application 501 ofsystem 210. Playback application 501 communicates to CCM 300, viaconnection 520, to determine whether incoming media 499 is protected byany copyright restrictions and/or licensing agreements. Playbackapplication 501 communicates with CCM 300 to control switches 311, 312,571, and 511, accordingly. In the present example, recording of incomingmedia 499 would violate applicable restrictions and/or agreements andtherefore switch 511 is in an open position, such that the output pathto recording application 502, e.g., wave-out line 548 and/or wave-outline 568 and/or wave-out line 588, is effectively blocked, therebypreventing unauthorized recording of media 499.

Still referring to FIG. 5D, it is particularly noted that although CCM300 can prevent unauthorized recording of incoming media 499 bycontrolling switches 311, 312, and 571, thus preventing incoming media499 from reaching recording application 502, controlling switches 311,312, and 571, do nothing to prevent incoming media 499 from beingreturned to recording application 502 by a kernel streaming mechanism515(e.g., DirectKS), which enables capturing and redirecting of incomingmedia 499 to recording application 502, via wave-out line 588. Thus, byalso controlling switch 511 of media device driver 505, CCM 300 canprevent kernel streaming mechanism 515 from returning incoming media 499to recording application 502, thereby preventing incoming media 499 frombeing captured and redirected to recording application 502 in an attemptto create and unauthorized copy and/or recording of incoming media 499.However, when switch 511 is in a closed position, incoming media 499 maybe returned to a recording application 502, such that recording could bepossible, provided recording does not violate copyright restrictionsapplicable to incoming media 499. Additionally, at any time duringplayback of media 499, switch 312 of custom media device 310, switch 311of wave shim driver 309, and/or switch 511 of media device driver 505can be dynamically activated by CCM 300.

FIG. 6A is an block diagram of a media file, e.g., incoming media 499,adapted to be received by a playback application, e.g., 501 of FIGS. 5A,5B, 5C, and 5D, configured with an indicator 605 for enabling incomingmedia 499 to comply with rules according to the SCMS (serial copymanagement system). When applicable to a media file, e.g., 499, the SCMSallows for one copy of a copyrighted media file to be made, but not forcopies of copies to be made. Thus, if incoming media 499 can be capturedby a recording application, e.g., 502 of FIGS. 5A, 5B, 5C, and/or 5D,and/or a recording device, e.g. 529, and/or a peripheral recordingdevice and/or a recording application coupled to a digital output of amedia hardware output device, e.g., digital output 575 of media hardwareoutput device 570 of FIGS. 5B, 5C, and 5D, and/or a kernel streamingmechanism 515, e.g., DirectKS of FIG. 5D, unauthorized copying and/orrecording may be accomplished.

Playback application 501 is coupled with CCM 300 via communication line520 in a manner analogous to FIGS. 5A, 5B, 5C, and/or 5D. Although notshown in FIG. 6, it is noted that CCM 300 is also coupled to switches311 and 511 as shown in FIG. 5A, switches 311 and 312 in FIG. 5B,switches 311, 312, and 571 in FIG. 5C, and switches 312, 311, 571, and511, in FIG. 5D.

In one embodiment, an indicator 605 is attached to incoming media 499for preventing unauthorized copying or recording in accordance with theSCMS. In one embodiment, indicator 605 can be a bit that may betransmitted prior to beginning the delivery of incoming media 499 toplayback application 501. In another embodiment, indicator 605 mayplaced at the beginning of the bit stream of incoming media 499. Inanother embodiment, indicator 605 may be placed within a frame period ofincoming media 499, e.g., every fifth frame, or any other desired frameperiod. In another embodiment, indicator 605 may be transmitted at aparticular time interval or intervals during delivery of the media file,e.g. incoming media 499. Thus, indicator 605 may be placed nearlyanywhere within or attached to the bit stream related to incoming media499.

Indicator 605 may be comprised of various indicators, e.g., a level 0indicator, a level 1 indicator, and a level 2 indicator, in oneembodiment of the present invention. In the present embodiment, a level0 indicator may be for indicating to CCM 300 that copying is permittedwithout restriction, e.g., incoming media 499 is not copyrighted or thatthe copyright is not asserted. In the present embodiment, a level 1indicator may be for indicating to CCM 300 that one generation of copiesof incoming media 499 may be made, such that incoming media 499 is anoriginal copy and that one copy may be made. In the present embodiment,a level 2 indicator may be for indicating to CCM 300 that incoming media499 is copyright protected and/or a copy thereof, and as such no digitalcopying is permitted.

For example, incoming media 499 is received by playback application 501.Application 501 detects an indicator 605 attached therewith, in thisexample, a level 2 bit is placed in the bit stream for indicating to CCM300 that copying is not permitted.

For example, when CCM 300 is configured in system 210 such as that shownin FIG. 5A, in response to a level 2 indicator bit, CCM 300, whilecontrolling the audio path, then activates switches 311 and 511 toprevent any recording of incoming media 499.

When CCM 300 is configured in system 210 such as that shown in FIG. 5B,in response to a level 2 indicator bit, CCM 300, while controlling theaudio path, then activates switches 311 and 312 to prevent any recordingof incoming media 499.

When CCM 300 is configured in system 210 such as that shown in FIG. 5C,in response to a level 2 indicator bit, CCM 300, while controlling theaudio path, then activates switches 311, 312, and 571 to prevent anyrecording of incoming media 499.

It is noted that CCM 300 can activate or deactivate switches coupledtherewith, as described herein with reference to FIGS. 5A, 5B, 5C, and5D, thereby funneling incoming media 499 through the secure media path,in this instance the audio path, to prevent unauthorized copying ofincoming media 499. It is further noted that CCM 300 can detect mediarecording applications and devices as described herein, with referenceto FIG. 3.

FIGS. 7A, 7B, and 7C, are a flowchart 700 of steps performed inaccordance with one embodiment of the present invention for controllingend user interaction of delivered electronic media. Flowchart 700includes processes of the present invention which, in one embodiment,are carried out by processors and electrical components under thecontrol of computer readable and computer executable instructions. Thecomputer readable and computer executable instructions reside, forexample, in data storage features such as computer usable volatilememory 104 and/or computer usable non-volatile memory 103 of FIG. 1.However, the computer readable and computer executable instructions mayreside in any type of computer readable medium. Although specific stepsare disclosed in flowchart 700, such steps are exemplary. That is, thepresent invention is well suited to performing various other steps orvariations of the steps recited in FIGS. 7A, 7B, and 7C. Within thepresent embodiment, it should be appreciated that the steps of flowchart700 may be performed by software, by hardware or by any combination ofsoftware and hardware.

The present embodiment provides a mechanism for restricting recording ofhigh fidelity media content delivered via one or more communicationnetworks. The present embodiment delivers the high fidelity mediacontent to registered clients while preventing unauthorized clients fromdirectly receiving media content from a source database. Once the clientcomputer system receives the media content, it can be stored in hiddendirectories and/or custom file systems that may be hidden to preventsubsequent unauthorized sharing with others. It is noted that variousfunctionalities can be implemented to protect and monitor the deliveredmedia content. For example, the physical address of the media contentcan be hidden from media content recipients. In another example, thedirectory address of the media content can be periodically changed.Additionally, an access key procedure and rate control restrictor canalso be implemented to monitor and restrict suspicious media contentrequests. Furthermore, a copyright compliance mechanism, e.g., CCM 300,can be installed in the client computer system 210 to provide clientside compliance with licensing agreements and copyright restrictionsapplicable to the media content. By implementing these and otherfunctionalities, the present embodiment restricts access to and thedistribution of delivered media content and provides a means forcopyrighted media owner compensation.

It is noted that flowchart 700 is described in conjunction with FIGS. 2,3, 4, 5A, 5B, 5C, and 5D, in order to more fully describe the operationof the present embodiment. In step 702 of FIG. 7A, a user of a computersystem, e.g., 210, causes the computer to communicatively couple to aweb server, e.g., 250, via one or more communication networks, e.g.,Internet 201, and proceeds to attempt to log in. It is understood thatthe log in process of step 702 can be accomplished in a variety of waysin accordance with the present invention.

In step 704 of FIG. 7A, web server 250 accesses a user database, e.g.,450, to determine whether the user and the computer system 210 loggingin are registered with it. If the user and computer system 210 areregistered with web server 250, the present embodiment proceeds to step714. However, if the user and computer system 210 are logging in for thefirst time, web server 250 can initiate a user and computer system 210registration process at step 706.

In step 706, registration of the user and computer system 210 isinitiated. The user and computer system registration process can involvethe user of computer system 210 providing personal informationincluding, but not limited to, their name, address, phone number, creditcard number, online payment account number, biometric identification(e.g., fingerprint, retinal scan, etc.), and the like. Web server 250can verify the accuracy of the information provided. Web server 250 canalso acquire information regarding the user's computer system 210including, but not limited to, identification of media players disposedand operable on system 210, a unique identifier corresponding to thecomputer system, etc. In one embodiment, the unique identifiercorresponding to the computer system can be a MAC address. Additionally,web server 250 can further request that the user of computer system 210to select a username and password.

In step 708 of FIG. 7A, subsequent to the completion of the registrationprocess, web server 250 generates a unique user identification (ID) oruser key associated with the user of client computer system 210. Theunique user ID, or user key, is then stored by web server 250 in amanner that is associated with that registered user. Furthermore, one ormore cookies containing that information specific to that user and theuser's computer system 210, is installed in a non-volatile memorydevice, e.g., 103 and/or data storage device 108 of computer system 210.It is noted that the user ID and cookie can be stored in a hiddendirectory within one or more non-volatile memory devices within computersystem 210, thereby preventing user access and/or manipulation of thatinformation. It is further noted that if the unique user ID, or userkey, has been previously generated for the user and computer 210 thatinitially logged-in at step 702, the present embodiment proceeds to step714

In step 710, web server 250 verifies that the user ID and the cookie(s)are properly installed in computer system 210 and verifies the integrityof the cookie(s) and the user ID, thereby ensuring no unauthorizedalterations to the user ID or the cookie has occurred. If the user ID isnot installed and/or not valid, web server 250 can re-initiate theregistration process at step 706. Alternatively, web server 250 candecouple computer system 210 from the network, thereby requiring are-log in by the user of computer 210. If the cookie(s) and user ID arevalid, the present embodiment proceeds to step 712.

In step 712 of FIG. 7A, web server 250 can install a version of acopyright compliance mechanism, e.g., 300, onto one or more non-volatilememory devices of computer system 210. Installing CCM 300 into user'scomputer system 210 can facilitate client side compliance with licensingagreements and copyright restrictions applicable to specific deliveredcopyrighted media content. At step 712, the components of CCM 300, suchas instructions 301, coder/decoder (codec) 303, agent programs 304,system hooks 305, skins 306, and custom media device drivers 307 (e.g.,custom media device 310 of FIGS. 5B, 5C, and 5D), are installed incomputer system 210, such as that shown in FIGS. 5A, 5B, 5C, and 5D. Inone embodiment, a hypertext transfer protocol file delivery system canbe utilized to install CCM 300 into computer system 210. However, step712 is well suited to install CCM 300 on computer system 210 in a widevariety of ways in accordance with the present embodiment. For example,CCM 300 can be installed as an integrated component within a mediaplayer application, media recorder application, and/or mediaplayer/recorder applications. Alternatively, CCM 300 can be installed asa stand alone mechanism within a client computer system 210.Additionally, CCM 300 can be installed as a stand alone mechanism and/oras part of a bundled application from a media storage device, e.g., aCD, a DVD, an SD, and/or as part of an installation package. In anotherembodiment, CCM 300 can be installed in conjunction with a presentationof desired media content, e.g., listening to an audio file on a musicCD, reading a document, viewing a video, etc. It is noted that, in oneembodiment, CCM 300 may be installed on client system 210 in aclandestine manner, relative to a user.

In step 714, web server 250 can request the previously establishedusername and password of the user of client computer system 210.Accordingly, the user of client computer system 210 causes it totransmit to web server 250 the previously established username andpassword. Upon the receipt thereof, web server 250 may access a userdatabase, e.g., 450, to determine their validity. If the username andpassword are invalid, web server 250 refuses access wherein flowchart500 may be discontinued (not shown). Alternatively, if the username andpassword are valid, the present embodiment proceeds to step 716.

In step 716 of FIG. 7A, web server 250 can access media file database450 to determine if copyright compliance mechanism 300 has been updatedto reflect changes made to the DMCA (digital millennium copyright act)and/or to the interactive/non-interactive licensing agreementsrecognized by the DMCA. It is noted that alternative licensingagreements can be incorporated into copyright compliance mechanism 300.Advantageously, by providing a copyright compliance mechanism that canbe readily updated to reflect changes in existing copyright restrictionsand/or the introduction of other types of licensing agreements, and/orchanges to existing media player applications, or the development of newmedia player applications, copyright compliance mechanism 300 canprovide compliance with current copyright restrictions.

Continuing with step 716, if web server 250 determines that CCM 300, orcomponents thereof, of computer 210 has been updated, web server 250initiates installation of the newer components and/or the most currentversion of CCM 300 into computer system 210, shown as step 718. If webserver 250 determines that the current version of CCM 300 installed onsystem 210 does not have to be updated, the present embodiment proceedsto step 720 of FIG. 7B.

In step 720 of FIG. 7B, the user of client computer system 210 causes itto transmit to web server 250, e.g., via Internet 201, a request for aplay list of available media files. It is noted that the play list cancontain all or part of the media content available from a contentserver, e.g., 251.

In step 722, in response to web server 250 receiving the play listrequest, web server 250 transmits to client computer system 210 a mediacontent play list together with the unique user ID associated with thelogged-in user. The user ID, or user key, can be attached to the mediacontent play list in a manner invisible to the user. It is noted thatthe media content in content server 251 can be, but is not limited to,high fidelity music, audio, video, graphics, multimedia, alphanumericdata, and the like. The media content play list of step 720 can beimplemented in diverse ways. In one example, web server 250 can generatea media content play list by combining all the available media contentinto a single play list. Alternatively, all of the media content titles,or different lists of titles, can be loaded from content server 251 andpassed to a CGI (common gateway interface) program operating on webserver 250 where the media titles, or differing lists of titles, can beconcatenated into a single dimensioned array that can be provided toclient computer system 210. It is understood that the CGI can be writtenin nearly any software computing language.

In step 724 of FIG. 7B, the user of client computer system 210 canutilize the received media content play list in conjunction with a mediaplayer application in order to cause client computer system 210 totransmit a request to web server 250 for delivery of desired mediacontent, and wherein the user ID is automatically included therewith.The media content play list provided to client computer system 210 byweb server 250 can enable the user to create one or more customized playlists by the user selecting desired media content titles. It is notedthat a customized media play list can establish the media content thatwill eventually be delivered to client computer system 250 and the orderin which the content will be delivered. Additionally, the user of clientcomputer system 250 can create one or more customized play lists andstore those play lists in system 250 and/or within web server 250. It isnoted that a customized play list does not actually contain the desiredmedia content titles, but rather the play list includes one or moreidentifiers associated with the desired media content that can include,but is not limited to, a song, an audio clip, a video clip, a picture, amultimedia clip, an alphanumeric document, or particular portionsthereof. In another embodiment, the received media content play list caninclude a random media content delivery choice that the user of clientcomputer system 210 can transmit to web server 250, with the user ID, torequest delivery of the media content in a random manner.

In step 726, upon receiving the request for media content from clientcomputer system 210, web server 250 determines whether the requestingmedia application operating on client computer system 210 is a validmedia application. One of the functions of a valid media application isto be a player of media content as opposed to an application thatdownloads media content in an unauthorized or unregulated manner. If webserver 250 determines that the media application operating on system 210is not a valid media application, the present embodiment proceeds tostep 727 which in one embodiment, redirects client computer system 210to a web site where the user of system 210 can download a valid mediaplayer application or to a software application which can identifyclient computer system 210, log system 210 out of web server 250 and/orprevent future logging-in for a defined period of time, e.g., 15minutes, an hour, a day, a week, a month, a year, or any specifiedamount of time. If web server 250 determines that the media applicationoperating on system 210 is a valid media application, the presentembodiment proceeds to step 728.

In step 728 of FIG. 7B, the present embodiment causes web server 250 todetermine whether the user ID (or user key) that accompanied the mediadelivery request sent by client computer system 210 is valid. If webserver 250 determines that the user ID is invalid, the presentembodiment proceeds to step 729 where client computer system 210 can belogged off web server 250 or client computer system 250 can be returnedto step 706 (of FIG. 7A) to re-register and to have another unique userID generated by web server 250. It is noted that the order in whichsteps 726 and 728 are performed can be altered such that step 728 can beperformed prior to step 726. If web server 250 determines that the userID is valid, the present embodiment proceeds to step 730.

In step 730, prior to web server 250 authorizing the delivery of theredirect and access key for the requested media file content, shown asstep 732, CCM 300 governs certain media player applications and/orfunctions thereof that are operable on client computer system 210. Thesegoverned functions can include, pause, stop, progress bar, save, etc. Itis noted that, in one embodiment, CCM 300 can utilize system hooks 305to accomplish the functionality of step 730.

In step 732 of FIG. 7C, the present embodiment causes web server 250 totransmit to client computer system 210 a redirection command along witha time sensitive access key (for that hour, day or for any definedperiod of time) thereby enabling client computer system 210 to receivethe requested media content. The redirection command can include a timesensitive address of the media content location within content server251. The address is time sensitive because, in one embodiment, thecontent server 251 periodically renames some or all of the media addressdirectories, thereby making previous content source addresses obsolete.Alternatively, the address of the media content is changed. In anotherembodiment, the location of the media content can be changed along withthe addresses. Regardless, unauthorized users and/or applications arerestricted from directly retrieving and/or copying the media contentfrom content server 251. Therefore, if someone with inappropriate orunlawful intentions is able to find where the media content is stored,subsequent attempts will fail, as the previous route no longer exists,thereby preventing future unauthorized access.

It is noted that in one embodiment of the present invention, theaddresses (or routes) of content server 251 that are actively coupled toone or more client computer systems (e.g., 210-230) are maintained whilefuture addresses, or routes, are being created for new client devices.It is further noted that as client computer systems are uncoupled fromthe media content source of content server 251, that directory address,or link, can be immediately changed, thereby preventing unauthorizedclient system or application access.

In another embodiment, the redirection of client computer system 210 tocontent server 251 can be implemented by utilizing a server networkwhere multiple servers are content providers, (e.g., 251), or by routinga requesting client computer system (e.g., 210, 220, or 230) throughmultiple servers. In yet another embodiment, the delivery of mediacontent from a central content provider (e.g., 251) can be routedthrough one or more intermediate servers before being received by therequesting client computer system, e.g., 210-230.

The functionality of step 732 is additionally well suited to providerecordation of the Internet Protocol (IP) addresses of the clientcomputer systems, e.g., 210, the media content requested and itstransfer size, thereby enabling accurate monitoring of royalty payments,clock usage and transfers, and media content popularity.

In step 734 of FIG. 7C, upon receiving the redirection command, thepresent embodiment causes the media playback application 501 (FIGS. 5A,5B, 5C, and 5D) operating on client computer system 210 to automaticallytransmit to content server 251 a new media delivery request which caninclude the time sensitive access key and the address of the desiredmedia content.

In step 726 of FIG. 7C, content server 251 determines whether the timesensitive access key associated with the new media delivery request isvalid. If content server 251 determines that the time sensitive accesskey is valid, the present embodiment proceeds to step 738 of FIG. 7C.However, if content server 251 determines that the time access key isnot valid, the present embodiment proceeds to step 737, a clientredirect.

In step 737, content server redirects client computer 210 to step 732(not shown) where a new access key is generated. Alternatively, step 737causes the present embodiment to return to step 704 of FIG. 7A. In yetanother embodiment, step 737 causes client computer system 210 to bedisconnected from content server 251.

In step 738 of FIG. 7C, content server 251 transmits the requested highfidelity media content to client computer system 210. It is noted thateach media content file delivered to client computer system 210 can havea header attached thereto, prior to delivery, as described withreference to FIG. 4. It is further noted that both the media content andthe header attached thereto can be encrypted. In one embodiment, themedia content and the header can be encrypted differently.Alternatively, each media content file encrypted differently. In anotherembodiment, groups of media files are analogously encrypted. It is notedthat public domain encryption mechanisms, e.g., Blowfish, and/ornon-public domain encryption mechanisms can be utilized.

Still referring to step 738, content server 251 transmits the requestedmedia content in a burst load (in comparison to a fixed data rate),thereby transferring the content to client computer system 210 as fastas the network transfer rate allows. Further, content server 251 canhave its download rate adapted to be equal to the transfer rate of thenetwork to which it is coupled. In another embodiment, the contentserver 251 download rate can be adapted to equal the network transferrate of the client computer system 210 to which the media content isbeing delivered. For example, if client computer system 210 is coupledto Internet 201 via a T1 connection, then content server 251 transfersthe media content at transmission speeds allowed by the T1 connectionline. As such, once the requested media content is transmitted to clientcomputer system 210, content server 251 is then able to transmitrequested media content to another client computer system, e.g., 220 or230. Advantageously, this provides an efficient means to transmit mediacontent, in terms of statistical distribution over time and does notoverload the communication network(s).

It is noted that delivery of the requested media content by contentserver 250 to client computer system 210 can be implemented in a varietyof ways. For example, an HTTP (hypertext transfer protocol) filetransfer protocol can be utilized to transfer the requested mediacontent as well as a copyright compliance mechanism 300 to client 210.In this manner, the copyright compliance mechanism as well as each mediacontent file/title can be delivered in its entirety. In anotherembodiment, content server 251 can transmit to client computer system250 a large buffer of media content, e.g., audio clips, video clips, andthe like.

In step 740 of FIG. 7C, upon receiving the requested high fidelity mediacontent from content server 251, the present embodiment causes clientcomputer system 210 to store the delivered media content in a mannerthat is ready for presentation, e.g., play. The media content is storedin client computer system 210 in a manner that restricts unauthorizedredistribution. For example, the present embodiment can cause the highfidelity media content to be stored in a volatile memory device,utilizing one or more hidden directories and/or custom file systems thatmay be hidden, where it may be cached for a limited period of time.Alternatively, the present embodiment can cause the high fidelity mediacontent to be stored in a non-volatile memory device, e.g., 103 or datastorage device 108. It is noted that the manner in which each of thedelivered media content file(s) is stored, volatile or non-volatile, canbe dependent upon the licensing restrictions and copyright agreementsapplicable to each media content file. It is further noted that in oneembodiment, when a user of client computer system 210 turns the computeroff or causes client computer system 210 to disconnect from the network,the media content stored in a volatile memory device is typicallydeleted therefrom.

Still referring to step 740, in another embodiment, the presentembodiment can cause client computer system 210 to store the receivedmedia content in a non-volatile manner within a media applicationoperating therein, or within one of its Internet browser applications(e.g., Netscape Communicator™, Microsoft Internet Explorer™, Opera™,Mozilla™, and the like) so that delivered media content can be used in arepetitive manner. Further, the received media content can be stored ina manner making it difficult for a user to redistribute in anunauthorized manner, while allowing the user utilization of the receivedmedia content, e.g., by utilizing one or more hidden directories and/orcustom file systems that may also be hidden. It is noted that by storingmedia content with client computer system 210 (when allowed byapplicable licensing agreements and copyright restrictions), contentserver 251 does not need to redeliver the same media content to clientcomputer system 210 each time its user desires to experience (e.g.,listen to, watch, view, etc.) the media content file.

In step 742 of FIG. 7C, the received media content file is then fed intoa media player application (e.g., playback application 501 of FIGS. 5A,5B, 5C, and 5D), which then runs it through a codec e.g., coder/decoder303 of CCM 300, in one embodiment. In response, coder/decoder 303 sendsan authorization request to the server, e.g., 251, with attachedauthorization data, as described herein. In response to receivingcodec's 303 authorization request, server 251 compares the receivedauthorization data with that stored in server 251, and subsequently, thepresent embodiment proceeds to step 744.

In step 744, the server 251 responds with a pass or fail authorization.If server 251 responds with a fail, such that the received authorizationdata is invalid, the present method can proceed to step 745, whereserver 251 can, in one embodiment, notify the user of client system 210,e.g., by utilization of skin 306, that there was an unsuccessfulauthorization of the requested media content file. It is noted thatalternative messages having similar meanings may also be presented tothe user of client computer system 210, thereby informing the user thatthe delivery failed. However, if the authorization data passes, thepresent method proceeds to step 746.

In step 746, server 251 transmits certain data back to the media playerapplication which enables the media player application to present thecontents of the media file via media playback application 501 of FIGS.5A, 5B, 5C, and 5D. In one embodiment, a decryption key can be includedin the transmitted data to decrypt the delivered media content file. Inanother embodiment, an encryption/decryption key can be included in thetransmitted data to allow access to the contents of the media file. Thepresent method then proceeds to step 748.

In step 748 of FIG. 7C, subsequent to media file decryption, the mediafile may be passed through CCM 300, e.g., a coder/decoder 303, to amedia player application operating on client computer system 210, e.g.,playback application 501 of FIGS. 5A, 5B, 5C, and 5D, which can thenaccess and utilize the delivered high fidelity media content, enablingits user(s) to experience the media content, e.g., listen to it, watchit, view it, or the like. In one embodiment of the present invention, aspecialized or custom media player may be involved in order toexperience the media content, e.g., skin 306 of FIG. 3. Skin 306 may beimplemented when CCM 300 cannot modify an industry standard media playerapplication to comply with copyright restrictions and/or licensingagreements in accordance with the DMCA. Alternatively, a specialized orcustom media player may not be needed to experience the media content.Instead, an industry standard media player can be utilized by clientcomputer system 210 to experience the media content. Typically, manymedia player applications are available and can include, but are notlimited to, Windows™ Media Player™ for PCs (personal computers), iTunes™Player or QuickTime™ for Apple computers, and XMMS player for computersutilizing a Linux operating system. Regardless of the media playerapplication utilized, while the media file is passed to the media playerapplication, e.g., in a frame by frame basis or in a buffer by bufferbasis, coder/decoder 303 will repeatedly ensure that CCM 300 rules arebeing enforced at any particular moment during media playback, shown asstep 750.

In step 750, as the media file content is delivered to the media playerapplication, e.g., media player application 501 of FIGS. 5A, 5B, 5C, and5D, periodically, e.g., after a specified number of frames, after adefined period of time, or any desired time or data period,coder/decoder 303 repeatedly determines whether or not all the rules areenforced, in accordance with rules as defined by CCM 300. If the rulesare not enforced, e.g., change due to a user opening up a recordingapplication (e.g., Total Recorder or alternative application) thepresent method proceeds to step 751. If the rules, in accordance withCCM 300, are enforced, the present method then proceeds to step 752.

In step 751 of FIG. 7C, if the rules according to CCM 300 are notenforced, the presentation of the media content is, in one embodiment,suspended or halted. In one embodiment, CCM 300 can selectively controlswitches 311 and 511 (FIG. 5A) to prevent output of incoming media 499(FIGS. 5A, 5B, 5C, and 5D) to a recording application 502 (FIGS. 5A, 5B,and 5C, via wave shim driver 309 and direct sound 504 respectively, thuspreventing unauthorized recording of incoming media 499. In anotherembodiment, CCM 300 can selectively control switches 311 and 312 (FIG.5B) to prevent output of incoming media 499 to recording application 502via wave shim driver 309 and custom media device 310, thus preventingunauthorized recording of incoming media 499. In yet another embodiment,CCM 300 can selectively control switches 311, 312, to not only preventincoming media 499 from being recorded in an unauthorized manner but canalso selectively control switch 571 (FIG. 5C) to prevent unauthorizedoutput of incoming media 499 via digital output 575 of media hardwareoutput device 570. In yet another embodiment, CCM 300 can selectivelycontrol switches 311, 312, 571, and 511 to a prevent kernel streamingmechanism 515, e.g., DirectKS of FIG. 5D, which can establish aconnection with media device driver 505 of FIG. 5D, from capturingincoming media content and returning it to a recording application(e.g., 502) to create an unauthorized recording of the media content. Inone embodiment, incoming media 499 may not be output from digital output575. In another embodiment, incoming media 499 may be output via digitaloutput 575 but in an inaudible manner, e.g., silence. In yet anotherembodiment, incoming media 499 be audible but recording functionalitycan be disabled, such that the media content cannot be recorded.

In step 752, if the rules are enforced in accordance with CCM 300,coder/decoder 303 retrieves a subsequent portion of the media contentthat is stored locally in client computer system 210. The newlyretrieved portion of the media file is then presented by the client'smedia player application, shown in the present method as step 748. Whilethe newly retrieved portion is presented, embodiments of the presentmethod then again perform step 750, then step 752 or 751, then step 748,then 750, etc., in a continual loop until the media file contents arepresented in their entirety. Advantageously, by constantly monitoringplaying media files, CCM 300 can detect undesired activities and enforcethose rules defined by CCM 300.

FIG. 8 is a diagram of an exemplary high-speed global media contentdelivery system 800, in accordance with one embodiment of the presentinvention. In one embodiment, system 800 can be utilized to globallydeliver media content, e.g., audio media, video media, graphic media,multimedia, alphanumeric media, etc., to a client computer system, e.g.,210, 220, and/or 230, in conjunction with a manner of delivery similarto that described herein. In one embodiment, system 800 includes aglobal delivery network 802 that can include multiple content servers,e.g., 804, 806, 808, 810, 812, 814, and 816, that can be locatedthroughout the world and which may be referred to as points of presenceor media delivery point(s). Each of content server 804-816 can store aportion, a substantial portion, or the entire contents of a mediacontent library that can be delivered to client computer systems via anetwork, e.g., Internet 201, or a WAN (wide area network). Accordingly,each of content server 804-816 can provide media content to of clientcomputer systems in its respective vicinity in the world. Alternatively,each content server can provide media content to a substantial number ofclient computer systems

For example, a media delivery point (MDP) 816, located in Tokyo, Japan,is able to provide and deliver media content from the media contentlibrary stored in its content database, e.g., 451, to client computersystems within the Asiatic regions of the world while a media deliverypoint 812, located in New York City, N.Y., USA, is able to provide anddeliver media content from its stored media content library to clientdevices within the Eastern United States and Canada. It is noted thateach city name, e.g., London, Tokyo, Hamburg, San Jose, Amsterdam, orNew York, associated with one of the media delivery points 804-816represents the location of that particular media delivery point or pointof presence. However, it is further noted that these city names areexemplary because media delivery points 804-816 can located anywherewithin the world, and as such are not limited to the cities shown inglobal network 802.

Still referring to FIG. 8, it is further noted that global system 802 isdescribed in conjunction with FIGS. 2, 3, 4, 5A-D, and 6, in order tomore fully describe the operation of embodiment of the presentinvention. Particularly, subsequent to a client computer system, e.g.,client computer system 210 of FIG. 2, interacting with a web server,e.g., web server 250 of FIG. 2, as described herein, web server 250, inone embodiment, can redirect client computer system 210 to receive thedesired media content from an MDP (e.g., 804-816) based on one or morediffering criteria.

For example, computer system 210 may be located in Brattleboro, Vt., andits user causes it to log-in with a web server 250 which can be locatedanywhere in the world. It is noted that steps 702-730 of FIGS. 7A and 7Bcan then be performed as described herein such that the presentembodiment proceeds to step 732 of FIG. 7C. At step 732, the presentembodiment can determine which media delivery points, e.g., 804, 806,808, 810, 812, 814, or 816, can subsequently provide and deliver thedesired media content to client computer system 210.

Still referring to FIG. 8, one or more differing criteria can beutilized to determine which media delivery point to select for deliveryof the desired media content. For example, the present embodiment canbase its determination upon which media delivery point is in nearestproximity to client computer system 210, e.g., media delivery point 816.This can be performed by utilizing the stored registration information,e.g., address, provided by the user of client computer system 210.Alternatively, the present embodiment can base its determination uponwhich media delivery point provides media content to the part of theworld in which client computer system is located. However, if each mediadelivery point (e.g., 804-816) stores differing media content, thepresent embodiment can determine which one can actually provide thedesired media content. It is noted that these are exemplarydetermination criteria and the embodiments of the present invention arenot limited to such implementation.

Subsequent to determination of which media delivery point is to providethe media content to client computer system 210 at step 732, web server250 transmits to client computer system 210 a redirection command tomedia delivery point/content server 812 along with a time sensitiveaccess key, also referred to as a session key, (e.g., for that hour,day, or any defined time frame) thereby enabling client computer system210 to eventually receive the requested media content. Within system800, the redirection command can include a time sensitive address of themedia content location within media delivery point 812. Accordingly, theNew York City media delivery point 812 can subsequently provide anddeliver the desired media content to client computer system 210. It isnoted that steps 732-742 and step 737 of FIG. 7C can be performed bymedia delivery point 812 in a manner similar to content server 251described herein.

Advantageously, by utilizing multiple content servers, e.g., mediadelivery point 804-816, to provide high fidelity media content to clientcomputer systems, e.g., 210-230, located throughout the world,communication network systems of the Internet 201 do not become overlycongested. Additionally, global network 802 can deliver media content toa larger number of client computer systems (e.g., 210-230) in a moreefficient manner. Furthermore, by utilizing communication technologyhaving data transfer rates of up to 320 Kbps (kilobits per second) orhigher, embodiments of the present invention provide for rapid deliveryof the media content in a worldwide implementation.

Referring still to FIG. 8, it is noted that media deliverypoints/content servers 804-816 of global network 802 can be coupled in awide variety of ways in accordance with the present embodiment. Forexample, media delivery point 804-816 can be coupled utilizing wiredand/or wireless communication technologies. Further, it is noted thatmedia delivery points 804-816 can be functionally coupled such that ifone of them fails, another media delivery point can take over andfulfill its functionality. Additionally, one or more web servers similarto web server 250 can be coupled to global network 802 utilizing wiredand/or wireless communication technologies.

Within system 800, content server/media delivery point 804 includes aweb infrastructure that, in one embodiment, is a fully redundant systemarchitecture. It is noted that each MDP/content server 806-816 of globalnetwork 802 can be implemented to include a web infrastructure in amanner similar to the implementation shown in MDP 804.

Specifically, the web infrastructure of media delivery point 804includes firewalls 818 and 820 which are each coupled to global network802. Firewalls 818 and 820 can be coupled to global network 802 indiverse ways, e.g., utilizing wired and/or wireless communicationtechnologies. Particularly, firewalls 818 and 820 can each be coupled toglobal network 702 via a 10/100 Ethernet handoff. However, system 800 isnot limited in any fashion to this specific implementation. It is notedthat firewalls 818 and 820 are implemented to prevent malicious usersfrom accessing any part of the web infrastructure of media del 836,e.g., a router or other switching mechanism, coupled therewith and a DB(database) server 840 coupled to device 836 while firewall 820 includesa device 838, e.g., a router or other switching mechanism, coupledtherewith and a DB (database) server 842 coupled to device 838.Furthermore, DB server 840 is coupled with device 838 and DB server 842is coupled with device 836.

Still referring to FIG. 8, and within media delivery point 804, firewall818 is coupled to a director device 822 which is coupled to internal webapplication server 826 and 828, and a hub server 830. Firewall 820 iscoupled to a director 824 which is coupled to internal web applicationservers 826 and 828, and hub server 830. Hub server 830 can beimplemented in a variety of ways including, but not limited to, as aLinux hub server. Hub server 780 is coupled to a data storage device 832capable of storing media content. Data storage device 832 can beimplemented in a variety of ways, e.g., as a RAID (redundant array ofinexpensive/independent disks) appliance.

It is noted that media delivery points 804-816 can be implemented in anymanner similar to content server 250 described herein. Additionally,media delivery points 804-816 of the present embodiment can each beimplemented as one or more physical computing devices, e.g., computersystem 100 of FIG. 1.

In another embodiment, CCM 300 can be adapted to be disposed on a mediastorage device, e.g., media storage device 999 of FIGS. 10 and 11. Mediastorage device 999 can be, but is not limited to, a CD, a DVD, or otheroptical or magnetic storage device. By virtue of disposing a version ofCCM 300 on a media storage device 999, embodiments of the presentinvention can provide copy protection for audio, video, multimedia,graphics, information, data, software programs, and other forms of mediathat may contain copyrighted material and which may be disposed on amedia storage device. Alternatively, CCM 300 can be adapted to beinstalled on a computer system, e.g., client computer system 210, via amedia storage device 999 upon which it may be disposed.

FIG. 9 is a block diagram of a copyright compliance mechanism/mediastorage device (CCM/MSD) 900, a version of CCM 300 adapted to bedisposed on a media storage device, e.g., media storage device 999 ofFIGS. 10 and 11. It is noted that CCM 300 in CCM/MSD 900 is analogous toCCM 300 as described in FIGS. 3, 4, 5A-D, 6A and 7A-C. Further, CCM/MSD900 can be readily updated in accordance with global delivery system800, as described in FIGS. 7A-C, and FIG. 8.

In one embodiment, CCM/MSD 900 is adapted to provide stand-alonecompliance with copyright restrictions and licensing agreementsapplicable to media files that may be disposed on a media storagedevice, e.g., media storage device 999. In another embodiment CCM/MSD900 is adapted to be installed on a computer system, e.g., clientcomputer system 210 to provide compliance with copyright restrictionsand licensing agreements applicable to media files as described in FIGS.3, 4, 5A-D, 6A and 7A-C.

Referring to FIG. 9, CCM/MSD 900 includes an autorun protocol component910 for invoking automatic installation of CCM 300. To deter users fromattempts at defeating various features inherent to CCM 300, e.g., theautorun feature, CCM 300's monitoring program, agent program 304,verifies that those features that are to be operational are operational,and if not, CCM 300 prohibits the user from experiencing the contents ofthe media storage device.

If a user somehow defeats the autorun feature, and the user attempts toutilize an application to capture an image of the content, theapplication will make an image of the content on the media storagedevice, which also images the copyright protection contained thereon,and when the image is played, CCM 300 recognizes the copy protection ispresent, and CCM 300 will only allow the user to experience the contentwhen authorized, once CCM 300 is installed.

By virtue of the protections as described above provided by CCM 300,users will be able to experience the content of the media storage devicein the content's original high quality format, thereby obviating theneed to compress the media file used on client system 210.Advantageously, the user will no longer need to suffer through poorquality output as a result of severely compressed media files.

It is noted that when adapted to be implemented in conjunction with asecure file format, meaning that the format of the file is, withoutproper authorization, non-morphogenic, embodiments of the presentinvention also provide effective compliance with copyright restrictionsand licensing agreements with secure files formats. CCM 300 can controlthe types of file formats into which the media file can be transformed,e.g., .wav, .mp3, etc.

In one embodiment, the autorun feature associated with media storagedevice drive 1112 of client system 210 is activated and operational.Alternatively, a notice of required autorun activation within clientsystem 210 may be displayed on the media storage device and/or the casein which the media storage device is stored.

In another embodiment, if CCM 300 is present or if the user is coupledto a server, then messages containing instructions on how to activatethe autorun feature of client system 210 may be presented to the user.

In one embodiment autorun protocol component 910 can detect mediastorage device drives resident on a computer system, e.g., clientcomputer system 210.

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting media storagedevice drives residing and operable on client computer system 210,according to one embodiment of the present invention.

 if ( (dwRetVal = GetLogicalDrives( ))  != (DWORD) 0) {  /* initializevariables */  dwMask = (DWORD) 1;  /* initialize path to root of currentdrive */  _tcscpy(szDrive, _T(“A:\\”));  for (nIndex = 0, dwMask =(DWORD) 1;   dwMask != (DWORD) 0;   nIndex++, dwMask <<= 1)  {   if((dwRetVal & dwMask) != 0)   {    /* construct path to root of drive */   szDrive[0] = (TCHAR) ‘A’ + nIndex;    if (GetDriveType(szDrive) ==DRIVE_CDROM)    {     MessageBox((HWND) 0,          _T(“CD-ROM drivefound.”),          szDrive,          MB_OK);    }    else    {     /*clear bit at current position */     dwRetVal &= (~dwMask);    }   }  }}

In another embodiment, autorun protocol component 910 can detect whethera media storage device containing media files has been inserted into amedia storage device drive coupled with client computer system 210,e.g., drive 1112 of FIG. 10. In another embodiment, CCM 300 can includeinstructions for monitoring media storage device drive 1112, and upondetection of drive activation, CCM 300 determines what type of mediastorage device has been inserted therein. Subsequently, CCM 300 candetect various triggers on the media storage device to invoke itsprotection, e.g., a hidden file on newer media storage devices and/orthe copyright indicator bit on legacy media storage devices, obviatingthe need for autorun. Upon detection, CCM 300 can invoke the appropriateprotection for the associated media file.

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting a media storagedevice inserted in a media storage device drive residing and operable onclient computer system 210, according to one embodiment of the presentinvention.

 /* set error mode for operation */ uiErrMode =SetErrorMode(SEM_FAILCRITICALERRORS); /* initialize path to root ofcurrent drive */ _tcscpy(szDrive, _T(“A:\\”)); for (nIndex = 0, dwMask =(DWORD) 1;  dwMask != (DWORD) 0;  nIndex++, dwMask <<= 1) {  if((dwCDROMMask & dwMask) != 0)  {   /* construct path to root of drive */  szDrive[0] = (TCHAR) ‘A’ + nIndex;   if ( GetDiskFreeSpace(szDrive,              &dwSectors,               &dwBytes,              &dwClustersFree,               &dwClusters)     != 0)   {    /* add bit for drive to mask */     dwRetVal |= dwMask;   }  } } /*restore original error mode */ SetErrorMode(uiErrMode);

Additionally, autorun protocol component 910 can also detect changes inmedia, e.g., insertion of a different media storage device 999. Further,other media changes can be detected subsequent to adaptation of thesource code including, but not limited to, detecting a previouslyaccessed media file, detecting a previously inserted media storagedevice.

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting a change inmedia, according to one embodiment of the present invention.

 /* initialize path to root of current drive */ _tcscpy(szDrive,_T(“A:\\”)); for (nIndex = 0, dwMask = (DWORD) 1;  dwMask != (DWORD) 0; nIndex++, dwMask <<= 1) {  /* check for presence of CD-ROM media indrive */  if ((dwCurrMask & dwMask) != 0)  {   /* check if mediapreviously in drive */   if ((dwPrevMask & dwMask) == 0)   {    /*construct path to root of drive */    szDrive[0] = (TCHAR) ‘A’ + nIndex;   /* check for presence of marker on drive */    if(IsMPBMarkerPresent(szDrive) != 0)    {     /* process autoruninformation present on drive */     nRetVal = ProcessAutorun(szDrive);   }   }  } }

Still referring to FIG. 9, CCM/MSD 900 also includes a kernel levelfilter driver 920 for controlling a data input path of an operatingsystem coupled with and operable on client computer system 210.

CCM/MSD 900 also includes a generalized filter driver 930 forcontrolling ripping and “burning” applications, e.g., Nero, Roxio, ExactAudio Copy, and others, thereby preventing such activities.

The following C++ source code is an exemplary implementation of aportion of generalized filter driver 930 for controlling ripping andburning applications that may be residing on and operable within clientcomputer system 210, in accordance with one embodiment of the presentinvention.

bool bDisabled;  /* flag indicating CD reads disabled */  /* initializevariables */  bDisabled = false;  if (bProtected == true)  {   if (type== IRP_MJ_DEVICE_CONTROL)   {    ULONG ulIoControlCode =stack- >Parameters.DeviceIoControl.IoControlCode;    if (ulIoControlCode== IOCTL_SCSI_PASS_THROUGH)    {     SCSI_PASS_THROUGH * pspt =    (SCSI_PASS_THROUGH *) Irp->AssociatedIrp.SystemBuffer;     if ((pspt != NULL)      && (pspt->Cdb[0] == SCSIOP_READ_CD))     {     pspt->DataTransferLength = 0;      pspt->ScsiStatus = 0;     bDisabled = true;     }    }    else if (ulIoControlCode ==   IOCTL_SCSI_PASS_THROUGH_DIRECT)    {     SCSI_PASS_THROUGH_DIRECT *psptd = (SCSI_PASS_THROUGH_DIRECT *) Irp->AssociatedIrp.SystemBuffer;    if( (psptd != NULL)      && (psptd->Cdb[0] == SCSIOP_READ_CD))     {     psptd->DataTransferLength = 0;      psptd->ScsiStatus = 0;     bDisabled = true;     }    }   }  }  if (bDisabled == true)  {   /*complete current request */   status = CompleteRequest(Irp,STATUS_SUCCESS, 0);  }  else  {   /* pass request down withoutadditional processing */   status =IoAcquireRemoveLock(&pdx->RemoveLock, Irp);   if (!NT_SUCCESS(status))   return CompleteRequest(Irp, status, 0);  IoSkipCurrentIrpStackLocation(Irp);   status =IoCallDriver(pdx->LowerDeviceObject, Irp);  IoReleaseRemoveLock(&pdx->RemoveLock, Irp);  }

Still referring to FIG. 9, CCM/MSD 900 includes a CCM 300, analogous toCCM 300 of FIG. 3, that is adapted to be installed in client computersystem 210 in the manner described herein.

In one embodiment, kernel level filter driver 920, generalized filterdriver 930 and CCM 300 of CCM/MSD 900 are automatically installed onclient computer system 210, subsequent to insertion of media storagedevice 999 into a media storage device drive, e.g., media storage devicedrive 1112 of FIGS. 10 and 11. Autorun protocol component 910, asdescribed above, detects insertion of media storage device 999 into anappropriate drive, and initiates installation of the components, e.g.,CCM 300, driver 920 and driver 930. In one embodiment, drivers 920 and930 may be temporarily installed and may be deleted upon removal ofmedia storage device 999 from media storage device drive 1112. In yetanother embodiment, drivers 920 and 930 may be installed in hiddendirectories and/or files within client computer system 210. In anotherembodiment, some components of CCM 300 can remain installed on clientsystem 210, e.g. the monitoring program (agent program 304). In stillanother embodiment, other components, e.g., the kernel level filterdriver 920, can be dynamically loaded and unloaded as necessary inaccordance with copyright restrictions and licensing agreementsapplicable to the media file.

Embodiments of the present invention utilize software, e.g., CCM/MSD900, that is placed on media storage device 999, in conjunction withcontrolling software CCM 300 installed on client computer system 210,and web server 250 and/or content server 251, wherein each component iscommunicatively coupled with the other via the Internet, therebyenabling dynamic updating of CCM 300 in the manner as described withreference to FIG. 4, and steps 716 and 718 of FIGS. 7A-C.

In the present embodiment, CCM/MSD 900 provides a stand alone DRM thatis far more sophisticated than existing DRM solutions. This is becauseCCM/MSD 900 goes into the data pathway of the operating system operableon client computer system 210 and obtains control of the data pathway,e.g., filter driver 1108 of FIG. 11, rather than exploitinginefficiencies or errors in the computer system.

FIG. 10 is a block diagram of a communicative environment 1000 forcontrolling unauthorized reproduction of protected media files disposedon a media storage device. Included in communicative environment 1000 isa media storage device drive 1112 coupled with a client computer system210 via a data/address bus 110. Client computer system 210 is coupledwith web server 250 and content server 251 via Internet 201. A mediastorage device 999, upon which a CCM/MSD 900 may be disposed, isinserted in media storage device drive 1112. Autorun protocol component910 detects the insertion and automatically invokes installation of CCM300, kernel level filter driver 920 and generalized filter driver 930from media storage device 999 into client computer system 210.Subsequent to installation, CCM 300 initiates a dynamic update with webserver 250 and/or content server 251, via Internet 201. By installingCCM 300 on client computer system, agent program 304 (FIG. 3) of CCM 300is able to control the integrity of the software. Additionally, byconferring with servers 250 and/or 251 via Internet 201 online, the CCM300 software version on media storage device 999 and installed on clientcomputer system 210 can be updated when circumventions occur and keptcurrent from platform to platform.

Advantageously, the monitoring mechanism of agent program 304 enablesconstant morphing of the version of CCM 300 disposed on media storagedevice 999 by communicating with server 250 and/or 260 and utilizing thedynamic update capabilities of global network 800 to readily update thatwhich has been installed on client computer system 210, via mediastorage device 999.

In one embodiment, the installation is performed clandestine withrespect to the user and is initiated by inserting media storage device999 into an appropriate media storage device drive, e.g. amagnetic/optical disk drive or alternative device drive coupled withclient system 210. If the user is not registered with CCM 300, asdescribed herein with reference to FIG. 4 and FIGS. 7A-7C, onceinstalled, CCM 300 initiates an update process with web server 250and/or content server 251 to readily include updates that have beeninvoked subsequent to release of the media file on media storage device999. By virtue of the dynamic update capabilities of CCM 300, regardlessof the version of CCM 300 on media storage device 999, CCM 300 providescompliance with copyright restrictions and licensing agreementsapplicable to the media file on media storage device 999.Advantageously, enabling dynamic adaptability of CCM 300 provides forcontinued interoperability with new and updated operating systems,advancements in electronic technology, communication technologies andprotocols, and the like, ensuring the effectiveness of CCM 300 into thefuture.

In another embodiment, if the user is a registered user with globaldelivery system 800, CCM 300 can detect which version is most current.Accordingly, when the version existing on client system 210 is morecurrent that the version (for install) on media storage device 999, CCM300 can bypass the install process and present the contents contained onmedia storage device 999 to the user for them to experience.

Further advantageous, this technology is backward compatible with mediastorage device drives manufactured subsequent to 1982. Additionally, CCM300 is compatible with media storage devices having a copyrightindicator bit disposed thereon. The copyright indicator bit has beenincluded on all CDs released since 1982.

In the present embodiment of FIG. 10, the media file is not encrypted onmedia storage device 999. In one embodiment, if the media file isencrypted on computer 210, it can be decrypted on the computer 210.However, home players and/or stand alone media playing devices rarelyinclude a decryption mechanism, and to experience the music on a homemachine, the music is conventionally not encrypted.

In one embodiment, an additional component of CCM 300 is that thetrigger for agent program 304 may be the copyright bit indicator. Thismeans when the copyright indicator bit is detected by CCM 300, thefunctions of CCM 300 are initiated. Alternatively, in anotherembodiment, when the copyright bit indicator is not detected, CCM 300may remain in an un-invoked or idle state. If CCM 300 can detect thecopyright bit indicator, CCM 300 can provide the appropriate compliancewith regard to copyright restrictions and licensing agreementsapplicable to the media files.

In an alternative embodiment, a trigger control in the table of contentsof a media storage device 999 includes instructions for triggeringautorun protocol 910 of CCM/MSD 900 and can utilize the copyrightindicator bit or alternative implementation to trigger the technology.In this manner, CCM 300 can control copyrighted works while publicdomain material can be experienced and reproduced at a user'sdiscretion. Because autorun is problematic for media storage devicemanufacturers, embodiments of CCM/MSD 900 can include alternativeautorun programs that perform analogous to autorun.

In another embodiment, CCM 300 can invoke its own proprietary player,e.g., custom media device 310 as described with reference to FIG. 3,thus enabling increased control of copyright restrictions and/orlicensing agreements applicable to the media. By invoking custom mediadevice 310, CCM 300 enables user experience of the media while providingprotection against unauthorized reproduction of the media disposed onmedia storage device 999.

In an alternative embodiment, the media files and the CCM/MSD 900disposed on a media storage device 999 are encrypted. Thisimplementation is particularly advantageous for demonstration (demo)versions of media files, beta test versions, and the like that may bedisposed on media storage device 999. It is noted that the presentembodiment is operable in an online environment, meaning that clientcomputer system 210 is communicatively coupled with web server 250and/or content server 251 to enable a user experience of the content ona demo version of media storage device 999. In this implementation, CCM300 allows for specific plays for specific users, which can becontrolled via a network, e.g., network 1000 of FIG. 10, and server 250and/or 251.

In another embodiment, CCM 300 can be implemented for demo and/orpre-release protection. In this embodiment, CCM 300 utilizessophisticated encryption technology to encrypt the table of contents andCCM 300 with an associated decrypted key located on client computersystem. Encrypting CCM 300 can also deter nefarious attempts to reverseengineer CCM 300. Decryption can be performed using an associateddecryption key. Alternatively, decryption can be performed by aproprietary or custom media player application resident on demo mediastorage device, e.g., 999.

The content of media storage device 999 is encrypted, using variouslevels of encryption to provide protection levels commensurate withcopyright holders desires and required protection. For example, mediastorage device 999 is delivered to a user or critic for the purposes ofreview, the user inserts media storage device 999 into the appropriatestorage device reader or connector coupled with the journalist'scomputer, and CCM 300 is installed on client system 200 in a mannerclandestine to the user. Once installed, CCM 300 initiates acommunication session with web server 250/content server 251, wherecontent server 251 can provide authorization for the user to experiencethe media on media storage device 999.

Accordingly, if the user, to whom demo media storage device 999 had beenreleased, had demo media storage device 999 stolen, or if the userallowed alternative parties try to experience the content of mediastorage device 999, the unauthorized party would have to try to crackthe encryption keys and the encryption of the actual content of mediastorage device 999, consuming non-trivial amounts of time.

Thus, CCM 300 is able to control which users receive authorization toexperience the media of media storage device 999, how many times theuser may experience the media, and CCM 300 may also define a period oftime until the media may no longer be accessible. This may enablecopyright holders to release the content on an authorized media storagedevice, e.g., 999, prior to pirated copies flooding the market.

Accordingly, a demo media storage device 999 may be configured such thata first user may get a copy, a second user may get a copy, and if it isknown that the second user will share the demo with a third and a fourthuser, then the known users would be enabled to experience the media.Advantageously, by virtue of defining which users can access andexperience the media, any unauthorized sharing of the media by one ofthe authorized users can be readily detected, and further sharing orexperiencing of the media may be halted. Additionally, because theauthorized user shared the media in an unauthorized manner, in a worsecase scenario, criminal charges could be filed against that user.

It is noted that placing CCM/MSD 900 on a media storage device, e.g.,999, so as to enable installation of CCM 300 on client system 210 is onemanner in which CCM 300 can be installed on client system 210. Analternative manner in which CCM 300 can be installed on client computersystem 210 is through “cross-pollination.” For example, webcastersbroadcast the media file to the user. The media file has a CCM 300coupled with the media file, and upon downloading the media file ontoclient computer system 210, embodiments of the present invention enablethe installation of CCM 300 onto client computer system 210. In anothermanner, CCM 300 is incorporated into and becomes part of an operatingsystem operational on client system 210. Alternatively, laws are passedthat mandate the inclusion of CCM 300 on each client computer system210.

FIG. 11 is an exemplary logic/bit path block diagram 1100 of a clientcomputer system, e.g., 210, configured with a copyright compliancemechanism (CCM) 300 for preventing unauthorized reproduction ofcopyrighted media according to an embodiment of the present invention.Copyright compliance mechanism 300 is, in one embodiment, coupled withand operational on client system 210 in any manner described withreference to FIGS. 4, 5A-5D, 6A, and 7A-7C, 9, and 10.

Diagram 1100 of FIG. 11 includes a media storage device mediaextraction/creation application 1102 communicatively coupled tooperating system input/output subsystem 1104 via wave in line 1121 andwave out line 1138. Operating system input/output subsystem 1104 iscoupled with media storage device class driver 1106 via wave in line1123 and wave out line 1136. Media storage device class driver 1106 iscoupled with filter driver 1108 via wave in line 1125 and wave out line1134. Filter driver 1108 is coupled with media storage device portdriver 1110 via wave in line 1127 and wave out line 1132. Filter driver1108 is shown to include a switch 1111, controlled by CCM 300 viacoupling 1160. Media storage device port driver 1110 is coupled withmedia storage device drive 1112 via wave line in 1129 and wave line out1130. Media storage device 999, shown to include CCM/MSD 900 isreceivable by media storage device drive 1112. Additionally, CCM 300 iscoupled with operating system input/output subsystem 1104 via wave inline 1150 and wave out line 1151.

In one embodiment, CCM 300 is coupled to and controls selectable switch1111 in filter driver 1108. Depending upon the copyright restrictionsand/or licensing agreements applicable to a media file disposed on mediastorage device 999, CCM 300 controls whether switch 1111 is open(shown), thus preventing the media file from reaching mediaextraction/creation application 1102, or closed (not shown) so as toallow reproduction of the protected media file. Mediaextraction/creation application 1102 can be a ripping or burningapplication such as Nero, Roxio, Exact Audio Copy, or other readilyavailable application.

Continuing with FIG. 11, media storage device 999 is received by mediastorage device drive 1112. CCM 300 determines whether media storagedevice 999 or media disposed thereon is protected by any copyrightrestrictions and/or licensing agreements, e.g., via detection of acopyright indicator bit. CCM 300 communicates with filter driver 1108 tocontrol switch 1111 accordingly. In the present example, reproducingmedia storage device 999, and/or the contents thereon, would violateapplicable restrictions and/or agreements and therefore switch 1111 isin an open position such that the output path to mediaextraction/creation application 1102, e.g., wave-out line 1138, iseffectively blocked thereby preventing unauthorized reproduction ofmedia storage device 999.

It is particularly noted that by virtue of CCM 300 controlling switch1111, and therefore controlling wave-out line 1138, any incomingcopyright protected media disposed on a media storage device 999 can beprevented from being reproduced in an unauthorized manner in accordancewith applicable copyright restrictions and/or licensing agreementsrelated to the incoming media.

Advantageously, as new secure or proprietary file formats are developed,CCM 300 can be readily adapted to be functional therewith. Further,CCM/MSD 900 can prevent users from making unauthorized reproductions ofmedia files, recording, copying, ripping, burning, etc. By using kernellevel filter drivers, e.g., filter driver 1108, and getting to a lowenough level within the operating system (OS) on client system 210, CCM300 can detect particular applications and when they request mediastorage device drive 1112 to poll the media file for copying, ripping,etc., and disable the data input path. CCM 300, in this embodiment,deals with the input pathway.

In one embodiment, alternative applications that monitor the state ofclient computer system 210 can enable the autorun functionality ofclient computer system 210 or alternatively, invoke an automaticmechanism similar to autorun to ensure invocation of CCM 300 forcompliance of copyright restrictions and/or licensing agreementsapplicable to media storage device 999 and/or the copyright protectedmedia disposed thereon.

In one embodiment, CCM 300 can invoke a proprietary media player frommedia storage device 999, or activate a proprietary media playerresident and operable on client computer system 210, or an alternativeauthorized media player resident on client computer system 210, asdescribed herein with reference to FIG. 3.

When media storage device 999 is a multisession device, e.g., a compactdisk having a data session and a music session (audio tracks), and it isinserted into media storage device drive 1112, CCM 300 looks at thecontents of the media storage device 999, and in some operating systemsthe audio tracks will not be displayed. Instead, the data session isshown, as is an autorun file, e.g., autorun protocol component 910, andupon clicking, invokes a player application. CCM 300 can have a datasession and files to which a user may not have access unless a playerapplication is invoked.

In one embodiment, the player application could deposit a monitoringportion (e.g., agent program 304) on client system 210, which in oneembodiment may reside on client computer system 210 subsequent toremoval of media storage device 999 from media storage device drive1112.

By virtue of content in a multisession media storage device 999, whichmay not be directly accessible to most player applications, at somepoint the player application will be invoked which can then install theCCM 300 into client system 210, according to one embodiment of thepresent invention.

In one embodiment, a proprietary media player application is stored onmedia storage device 999. However, it is not automatically invoked. Uponsome user intervention, e.g., inserting media storage device 999 intomedia storage device drive 1112, the media player application is loadedonto client system 210 which has CCM 300 integrated therewith. Thus, CCM300 is launched regardless of autorun being activated or not activated,and mandates the user to utilize the proprietary media playerapplication to experience the content of the media files on the mediastorage device. 999.

In an alternative embodiment, client computer system 210 has autorunoff, wherein it is common for the user to be unable to play a media fileunless a proprietary media player application is invoked. Activating theproprietary media player application can initiate an installation ofthose components of CCM 300 that are bypassed when autorun is notactive.

Advantageously, by providing a copyright compliance mechanism, e.g.,300, which can be easily and readily installed on a client computersystem, e.g., 210, embodiments of the present invention can beimplemented to control access to, the delivery of, and the user'sexperience with media content subject to copyright restrictions and/orlicensing agreements, for example, as defined by the DMCA. Additionally,by closely associating a client computer system, e.g., 210, with theuser thereof and the media content they receive, embodiments of thepresent invention further provide for accurate royalty recording.

FIG. 12 is a block diagram of a usage compliance mechanism 1200, analternative version of copyright compliance mechanism 300 which isconfigured to be disposed on a media storage device, e.g., media storagedevice 999 of FIGS. 10, 11, 13, 14, and 15 in one embodiment of thepresent invention. It is noted that CCM 300 in usage compliancemechanism 1200 is analogous to CCM 300 as described herein withreference to FIGS. 3, 4, 5A-5D, 6A, 7A-7C, 8, 9, 10, and 11. Further,usage compliance mechanism 1200 can be readily updated in accordancewith global delivery system 800, as described herein with reference toFIGS. 7A-7C, and FIG. 8.

In one embodiment, usage compliance mechanism 1200 is adapted to bedisposed on a media storage device 999. Content disposed thereon can, inone embodiment, be demonstration and/or pre-release content. Examples ofdemonstration and/or pre-release content can include, but is not limitedto, audio, video, multimedia, graphics, information, data, softwareprograms, etc. Demonstration and/or pre-release content can contain, butis not limited to, digital movies or music that may be distributed topersons in the related media field for review, e.g., a motion pictureacademy member for their review of a movie, a record industry critic toreview songs that may be released on a new compact disc, etc.Alternatively, demonstration and/or pre-release content can alsocontain, but is not limited to, a beta version of a software program,and the like.

Alternatively, the content disposed on media storage device 999 can, inanother embodiment, be a commercial release of audio content, videocontent, software application, etc. Embodiments of the present inventionare well suited to be implemented in a commercial environment, e.g.,public presentation systems such as those in movie theaters,auditoriums, arenas and the like. Additionally, embodiments of thepresent invention are readily adaptable to be implemented in commercialdistribution points, e.g., audio, video, and/or software retail and/orrental establishments, as well as for pay-per-view and/or pay-per-playimplementations.

Further, literary works, documents, graphics such as pictures, painting,drawing, and the like can comprise the content on a media storagedevice. It is noted that a nearly endless variety of demonstration,pre-release, and/or commercially released content can be disposed on amedia storage device 999.

Referring to FIG. 12, usage compliance mechanism (UCM) 1200 includes anautorun protocol 910 for invoking installation of components of UCM 1200on a client computer system, e.g., 210, in one embodiment of the presentinvention. Autorun protocol 910 of FIG. 12 is analogous to autorunprotocol 910 of FIG. 9. Also included in UCM 1200 is a file systemfilter driver 1220, in one embodiment of the present invention.

File system filter driver 1220 can, in one embodiment, be an upper leveland/or lower level filter for the individual bus devices within clientcomputer system 210, e.g., media storage device drive 1112 of FIGS. 10,11, 13, 14, and 15. File system filter driver 1220 is enabled to hookonto access to a media storage device drive 1112, e.g., a CD drive, andintercept data reads associated with accessing the content on a mediastorage device, e.g., media storage device 999.

File system filter driver 1220 includes a decrypter 1221 for providingdecryption of encryptions applied to encrypted content, e.g.,encryptions 2351-2N applied to encryptions 1351-1N of media content2001-N of FIG. 13, in one embodiment of the present invention. Decrypter1221 can provide dynamic decryption of encryptions applied to encryptedmedia content on a media storage device 999 as the content, e.g.,2001-N, is accessed and read by media storage device drive 1112.

Still referring to FIG. 12, UCM 1200 also includes a secure media player1210. Secure media player 1210 can be, in one embodiment, similar tocustom media device 310, an emulation of the custom media device driver307, as described herein with reference to FIGS. 3 and 5B-5D.Alternatively, secure media player 1210 may be an alternative mediaplayer having controlling properties analogous to custom media device310. Secure media player 1210 includes a decrypter 1211 for decryptingencryption applied to each instance of media disposed on a media storagedevice 999, e.g., encryptions 1351 to 1N applied to media content 2001to N of FIG. 13, respectively. Secure media player 1210 also includes awatermarker 1212 for watermarking the outgoing data stream. In oneembodiment, watermarker 1212 operates concurrent with secure mediaplayer 1210 and during player 1210's rendering of the content,watermarker 1212 will attach a serial number, e.g., serial number 1380of FIG. 13, associated with each media storage device 999 onto theoutgoing data stream.

FIG. 13 is a block diagram of contents and components that may bedisposed on a media storage device, e.g., 999, in accordance withembodiments of the present invention. FIG. 13 is shown with multipleinstances of content, e.g. media content 2001-200N, disposed thereon.Media content 2001-N may be, but are not limited to, movies, audiotracks, beta software, documents, literary works, etc. It is noted thatany digital media can be disposed on a media storage device 999 or on aplurality of media storage devices 999.

Media storage device 999 of FIG. 13 is analogous to media storage device999 of FIGS. 10 and 11, 14, and 15. In one embodiment of the presentinvention. media storage device 999 is configured for utilization inconjunction with demonstration and/or pre-release content.

Media storage device 999 of FIG. 13 is shown to have disposed thereon aUCM (usage compliance mechanism) 1200 for controlling presentation ofcontent, e.g., media content 2001-N, disposed on media storage device999. The UCM 1200 in FIGS. 13, 14, and 15, is analogous to the UCM 1200described herein with reference to FIG. 12. It is noted that autorunprotocol 910 of UCM 1200 is, in one embodiment, disposed on mediastorage device 999 in a non-encrypted form.

Also shown on media storage device 999 is a unique identifier forproviding a unique identification of the media storage device, e.g.,serial number 1380, in one embodiment of the present invention. Serialnumber 1380 may be, but is not limited to, nearly any distinguishableidentifying type of indicator, e.g., a randomly generated number, asequential number, a combination of numbers and alphanumeric characters,and the like.

Advantageously, by disposing a unique identifier on a media storagedevice 999, e.g. a serial number 1380, this enables close association ofthe content disposed thereon, e.g., media content 2001-N, with theanticipated recipient of the media storage device, e.g., a movie critic,a music critic, an academy award member, a software beta tester, etc.Therefore, by closely associating a media storage device, e.g., 999,with an anticipated recipient, e.g., the user of computer system 210,embodiments of the present invention can prevent unauthorized personsfrom experiencing content on a media storage device, as described hereinwith reference to FIGS. 3, 4, 7A-7C, and 8. Further advantageous is thatby having a unique identifier for each media storage device 999,embodiments also provide security at the media storage device masteringlevel. This means that an employee working at a mastering facility whounlawfully purloins a copy of the media storage device may still be ableto copy the contents and turn those copies into bootleg (unauthorizedversions) copies of the media storage device in an attempt to flood themarket. However, by virtue of each media storage device 999 having aunique identifier, and each media storage device 999 is associated withits intended recipient, persons not associated with a particular mediastorage device 999 will be unable to experience the content thereon.While the market may still be flooded with bootleg copies, those thatacquire a bootleg copy of a media storage device 999, in accordance withthe present invention, will not be able to experience the contentthereon, thereby possibly causing the public to be less receptive to theidea of an inexpensive bootleg copy of something that they cannot use.

In one embodiment, media storage device 999 may be distributed to itsintended recipients in a variety of ways. Ways to distribute mediastorage device 999 to its intended recipients can include, but is notlimited to, postal delivery methods, e.g., the United States PostalService, parcel delivery services such UPS (United Parcel Service)and/or Federal Express, courier delivery services, and the like. Inanother embodiment, the intended recipient of a media storage device 999may be required to physically pick up device 999 from a distributionpoint.

Also shown on media storage device 999 are multiple instances ofcontent, e.g., media content 2001-N, in one embodiment of the presentinvention. Media content 2001-N can be any type of digital mediacontent, including, but not limited to, audio, video, multimedia,graphics, information, data, software programs, etc.

Still referring to FIG. 13, in one embodiment of the present invention,each instance of media 2001-N is subject to a first encryption, e.g.,encryptions 1351 to 1N, respectively. In one embodiment, a firstdecryption key for each encryption, e.g., encryptions 1351-1N, may bestored in a server, e.g., web server 250 and/or content server 251 ofFIGS. 2, 4, 10, and 14. In one embodiment, secure media player 1210 canutilize decrypter 1211 and the decryption key stored on web server 250and/or content server 251 and decrypt encryptions 1351-1N duringrendering of the content. It is noted that secure media player 1210 iscommunicatively coupled with web server 250 and/or content server 251during rendering and presentation of the content disposed on mediastorage device 999.

Additionally, media content 2001-N having a first encryption appliedthereto, e.g., encryptions 1351-1N, are each subject to a secondencryption, e.g., encryptions 2351-2N, respectively, prior to disposalof media content 2001-N on a media storage device 999. In oneembodiment, a second decryption key to decrypt encryptions 2351-2N maybe stored in a server, e.g., web server 250 and/or content server 251 ofFIGS. 2, 4, 10, and 14. In one embodiment, file system filter driver1220 can utilize decrypter 1221 and the second decryption key stored onweb server 250 and/or content server 251 and decrypt encryptions 2351-2Nduring reading of the content on media storage device 999 by mediastorage device drive 1112. It is noted that file system filter driver1220 is communicatively coupled with web server 250 and/or contentserver 251 during rendering and presentation.

In one embodiment, encryptions 1351-1N can be less computationallyintensive encryptions than encryptions 2351-2N. Alternatively, in oneembodiment, encryptions 1351-1N can be more computationally intensivethan encryptions 2351-N.

There are many available encryption methods that can be implemented asencryptions 1351-1N and/or encryptions 2351-2N. Examples of encryptionsthat may be implemented as encryptions 1351-1N and/or 2351-2N caninclude, but are not limited to, triple DES, AES, Blowfish, and numerousothers. In one embodiment, encryptions 1351-1N and/or 2351-2N can eachbe comprised of a series and/or a mixture of encryptions. A differingencryption, e.g., a plurality of randomly generated encryptions, can beimplemented for each instance of media on a media storage device, ratherthan using one format. In one embodiment, numerous variations ofBlowfish are utilized to provide the desired encryptions.

Advantageously, by utilizing multiple differing encryptions for eachinstance of media, e.g., 2001-N, if a person/hacker attempts to gainaccess to the content by breaking encryption applied to a media content,e.g., second encryption 2352 applied to encrypted media content 2002,and succeeds, they have simply broken the second encryption for mediacontent 2002. However, the remaining encryption 1352 remains unbroken byvirtue of the differing encryptions. Therefore, the person/hacker wouldhave to perform the entire encryption breaking process again to accessmedia content 2002 on media storage device 999. Thus, after spendingnon-trivial amounts of time breaking two differing encryptions appliedto an instance of media, e.g., content 2002, the remaining content onmedia storage device 999 is still encrypted, each with its own differingmultiple encryption.

FIG. 14 is a block diagram of a communicative environment 1400 forcontrolling presentation of media content disposed on a media storagedevice. Included in communicative environment 1400 is a media storagedevice drive 1112 coupled with a client computer system 210 via adata/address bus 110. Client computer system 210 is coupled with webserver 250 and/or content server 251 via Internet 201. A media storagedevice 999, upon which a usage compliance mechanism 1200 may bedisposed, is inserted in media storage device drive 1112. Autorunprotocol component 910 detects the insertion and automatically invokesinstallation of CCM 300, file system filter driver 1220 and secure mediaplayer 1210 from media storage device 999 into client computer system210. Subsequent to installation, UCM 1200 initiates a dynamic updatewith web server 250 and/or content server 251, via Internet 201, asdescribed herein with reference to FIGS. 3, 4, and 7A-7C, therebycontrolling the integrity of the software. Additionally, by conferringwith servers 250 and/or 251 via Internet 201 online, the UCM 1200software version on media storage device 999 and installed on clientcomputer system 210 can be updated when circumventions occur and keptcurrent from platform to platform.

Advantageously, the monitoring mechanism of agent program 304 enablesconstant morphing of the version of CCM 300 disposed on media storagedevice 999 by communicating with server 250 and/or 251 and utilizing thedynamic update capabilities of global network 800 to readily update thatwhich has been installed on client computer system 210, via mediastorage device 999.

In one embodiment, the installation is performed clandestine withrespect to the recipient of media storage device 999 and is initiated byinserting media storage device 999 into an appropriate media storagedevice drive, e.g. a magnetic/optical disk drive or alternative devicedrive coupled with client system 210. Portions of UCM 1200 determine ifthe recipient is registered with web server 250 and/or content server251. If the recipient is not registered with servers 250 and/or 251, asdescribed herein with reference to FIG. 4 and FIGS. 7A-7C, and FIG. 8,portions of UCM 1200 initiates an installation process as describedherein with reference to FIGS. 3, 4, 7A-7C, and 11.

If computer system 210 is registered with servers 250 and/or 251, UCM1200 can initiate an update process with web server 250 and/or contentserver 251 to readily include updates that have been invoked subsequentto distribution of media storage device 999. By virtue of the dynamicupdate capabilities of UCM 300, regardless of the version of CCM 300 onmedia storage device 999, UCM 1200 provides compliance with copyrightrestrictions and licensing agreements applicable to the media content onmedia storage device 999, e.g., media content 2001-N. Advantageously,enabling dynamic adaptability of UCM 1200 provides for continuedinteroperability with new and updated operating systems, advancements inelectronic technology, communication technologies and protocols, and thelike, ensuring the effectiveness of UCM 1200 into the future.

In another embodiment, if the user is a registered user with globaldelivery system 800, UCM 1200 can detect which version is most current.Accordingly, when the version existing on client system 210 is morecurrent that the version (for install) on media storage device 999, UCM1200 can bypass the install process and present the contents containedon media storage device 999 to the user for them to experience.

Further advantageous, this technology is backward compatible with mediastorage device drives manufactured subsequent to 1982. Additionally, UCM1200 is compatible with media storage devices having a copyrightindicator bit disposed thereon. The copyright indicator bit has beenincluded on all CDs released since 1982.

In the present embodiment of FIG. 14, each instance of media isencrypted on media storage device 999, as described herein withreference to FIG. 13. However, most home players and/or stand alonemedia playing devices rarely include a decryption mechanism, and toexperience the music on a home machine, the music is conventionally notencrypted. Accordingly, media storage device 999, in its presentembodiment, may not be operable on a home and/or stand alone mediaplaying device.

In one embodiment, UCM 1200 can invoke its own proprietary player, e.g.,secure media player 1210, as described with reference to custom mediadevice 310 of FIG. 3, thus enabling increased control of copyrightrestrictions and/or licensing agreements applicable to the mediacontent. By invoking a secure media player 1210, UCM 1200 enables userexperience of media content while providing protection againstunauthorized presentation of reproduction of the media disposed on mediastorage device 999.

Still referring to FIG. 14, in one embodiment, the media content, e.g.,media content 2001-N, and UCM 1200 disposed on a media storage device999 are encrypted, with the exception of autorun protocol 910, asdescribed above. In one embodiment of the present invention, UCM 1200 isencrypted differently than media content 2001-N, thereby preventing thecracking of one encryption from being utilized on another encryption.This implementation is particularly advantageous for demonstration(demo) versions of media files, beta test versions, and the like thatmay be disposed on media storage device 999. It is noted that thepresent embodiment is operable in an online environment, meaning thatclient computer system 210 is communicatively coupled with web server250 and/or content server 251 to enable a user experience of the contenton a demo version of media storage device 999. In this implementation,UCM 1200 allows for specific plays for specific users, which can becontrolled via a network, e.g., network 1400 of FIG. 14, and server 250and/or 251.

In the present embodiment, UCM 1200 can be implemented for demonstrationand/or pre-release protection of content disposed on a media storagedevice 999. However, content disposed on media storage device 999 canalso be commercially released content, e.g., audio, video, software, andthe like. In this embodiment, sophisticated encryption technology, e.g.,Blowfish, is utilized to encrypt media content 2001-N on media storagedevice 999 with an associated decrypter key located on web server 250and/or content server 251. In one embodiment, a plurality of encryptionsare applied to media content 2001-N and a plurality of decrypter keysare stored on web server 250 and/or content server 251. Decryption canbe performed using an associated decryption key in conjunction with asecure media player 1210 and file system filter driver 1220 installed oncomputer system 210 via media storage device 999.

Still with reference to FIG. 14, the content of media storage device999, e.g., media content 2001-N is encrypted, using various levels ofencryption to provide protection levels commensurate with copyrightholders desires and required protection. For example, media storagedevice 999 is delivered to a user or critic for the purposes of review,the user inserts media storage device 999 into the appropriate storagedevice reader or connector coupled with the recipient's computer, andautorun protocol 910 initiates UCM 1200 install of CCM 300, file systemfilter driver 1220, secure media player 1210 on client system 210 in amanner clandestine to the user. Once installed, UCM 1200 initiates acommunication session with web server 250/content server 251, wherecontent server 251 can provide authorization for the user to experiencethe media on media storage device 999.

Accordingly, if the user, to whom demo media storage device 999 had beenreleased, had demo media storage device 999 stolen, or if the userallowed alternative parties try to experience the content of mediastorage device 999, the unauthorized party would have to try to crackthe encryption keys and the encryption of the actual content of mediastorage device 999, consuming non-trivial amounts of time.

Thus, UCM 1200 is able to control which recipients receive authorizationto experience the media content on media storage device 999, how manytimes the recipient may experience the media, and UCM 1200 may alsodefine a period of time until the media content may no longer beaccessible. This may enable copyright holders to release the mediacontent on an authorized media storage device, e.g., 999, prior topirated copies flooding the market.

Still referring to FIG. 14, accordingly, a media storage device 999 maybe configured such that a first user may get a copy, a second user mayget a copy, and if it is known that the second user will share the demowith a third and a fourth user, then the known users would be enabled toexperience the media. Advantageously, by virtue of defining which userscan access and experience the media, any unauthorized sharing of themedia by one of the authorized users can be readily detected, andfurther sharing or experiencing of the media may be halted.Additionally, because the authorized user shared the media in anunauthorized manner, in a worse case scenario, criminal charges could befiled against that user.

It is noted that placing UCM 1200 on a media storage device, e.g., 999,so as to enable installation of CCM 300 on client system 210 is onemanner in which CCM 300 can be installed on client system 210. Analternative manner in which CCM 300 can be installed on client computersystem 210 is through “cross-pollination.” For example, webcastersbroadcast the media file to the user. The media file has a CCM 300coupled with the media file, and upon downloading the media file ontoclient computer system 210, embodiments of the present invention enablethe installation of CCM 300 onto client computer system 210. In anothermanner, CCM 300 is incorporated into and becomes part of an operatingsystem operational on client system 210. Alternatively, laws are passedthat mandate the inclusion of CCM 300 on each client computer system210.

FIG. 15 is an exemplary logic/bit path block diagram 1500 of a clientcomputer system, e.g., 210, configured with a usage compliance mechanism1200 for controlling presentation of content on a media storage device999, in accordance with one embodiment of the present invention. Usagecompliance mechanism 1200 of FIG. 15 is analogous to usage compliancemechanism 1200 of FIG. 12. Therefore, CCM 300 of usage compliancemechanism 1200 is analogous to a copyright compliance mechanism 300coupled with and installed on a client computer system, e.g., 210, asdescribed herein with reference to FIGS. 3, 4, 5A-5D, 6A, 7A-7C, 8, 9,10, 1114, 15, and 16.

Diagram 1500 of FIG. 15 includes a media storage device drive 1112coupled with a media storage device file system driver 1114 via line1571. Media storage device drive file system driver 1114 enables anoperating system, e.g., Windows by Microsoft, Apple by Apple, Linux byLinux, etc., on a client computer system, e.g., client 210, to recognizeand control the media storage device drive, e.g., drive 1112. Coupled tomedia storage device drive file system driver 1114 is file system filterdriver 1220, via line 1572. Coupled to file system filter driver 1220 isa secure media player 1210 via line 1573. Coupled with secure mediaplayer 1210 are an operating system media subsystem 503 via line 1577and a media hardware output device 1370 via line 1574. UCM 1200 iscoupled with operating system media subsystem 503 via line 1576.

Media storage device drive 1112 of FIG. 15 is analogous to media storagedevice drive 1112 of FIGS. 11 and 15. Media storage device drive 1112 isconfigured to receive a media storage device 999, where media storagedevice 999 is appropriate for drive 1112. In one embodiment, drive 1112may be a CD drive and accordingly, media storage device 999 would be aCD. In another embodiment, drive 1112 may be a DVD drive andaccordingly, media storage device 999 would be a DVD, and so on.Therefore, media storage device drive 1112 can, when so configured,receive any media storage device 999 upon which data or content may bedisposed.

File system filter driver 1220 can be an upper level and/or lower levelfilter for the individual bus devices within client computer system 210,e.g., media storage device drive 1112, and is analogous to file systemfilter driver 1220 of FIG. 12. File system filter driver 1220 is able tohook onto access to a media storage device drive 1112, e.g., a CD drive,and intercept data reads associated with accessing the content, e.g.,media content 2001-N, on a media storage device, e.g., media storagedevice 999. File system filter driver 1220 is also enabled, viadecrypter 1221 and a decrypter key on servers 250 and/or 251, to providedynamic decryption of encrypted media content on a media storage device999 as the content is accessed and read by media storage device drive1112.

By virtue of file system filter driver 1220 operating at a file systemlevel instead of operating at a device drive class level, e.g., a CDclass level, it is able to recognize which files are being accessed frommedia storage device 999 for a particular operation. Advantageously,this obviates the need for a file system to be implemented within adriver for determining whether data that is being read needs decrypting.

Still referring to FIG. 15, secure media player 1210 is analogous tosecure media player 1210 of FIG. 11. Secure media player 1210 can, inone embodiment, be a custom media device 310 emulated by a custom mediadevice driver 307, as described herein with reference to FIG. 3. Inanother embodiment, secure media player 1210 can be a proprietary playerconfigured for utilization with demonstration and/or pre-release contentdisposed on a media storage device, e.g., media content 2001-N. Otherauthorized media players may also be used to present media content on amedia storage device 999, provided the other media players can complywith usage restrictions and licensing agreements applicable to the mediacontent and provided by secure media player 1210.

Media hardware output device 1370 is an appropriate output device forthe media content on media storage device 999. If media content 2001-Nare audio tracks or songs, then output device 1370 is an audio or soundcard for outputting music via speakers. Alternatively, if media content2001-N are video tracks, movies, literary works, software programs,etc., then output device 1370 is a graphics card for outputting movies,text, and the like via a display device, e.g., display device 105 ofFIG. 1.

Continuing with FIG. 15, a media storage device 999 is received by amedia storage device drive 1112. Autorun protocol 910 initiates aprocess to determine the presence of a usage compliance mechanism 1200and a secure media player 1210 operable on computer system 210. Ifeither and/or both usage compliance mechanism 1200 and secure mediaplayer 1210 are not present on computer system 210, autorun protocolinitiates installation of the components, as described herein withreference to FIGS. 3, 4, 5A-5D, 6, 7A-7C, 8-16. If UCM 1200 and securemedia player 1210 are both present, autorun 910 bypasses theinstallation thereof. Media storage device file system driver 1114accesses the content on media storage device, e.g., media content2001-N, and reads the data.

File system filter driver 1220 intercepts the read operation beingperformed by driver 1114 and dynamically decrypts a second encryptionapplied to media content 2001-N, e.g., encryptions 2351-2N of FIG. 13,via decrypter 1221 and a second decryption key stored on and retrievedfrom servers 250 and/or 251. In one embodiment, if file system filterdriver 1220 is not communicatively coupled with server 250 and/or 251,thereby enabled to retrieve the second decryption key, presentation ofthe content on a media storage device 999 is not permitted.

Continuing with FIG. 15, subsequent to second encryptions 2351-2N beingdecrypted, media content 2001-N, still encrypted with a firstencryption, e.g., encryptions 1351-N, respectively, is output to securemedia player 1210 via line 1573. Secure media player 1210 in conjunctionwith UCM 1200 communicates with server 250 and/or 251 and determines ifcomputer system 210 and the user thereof, are authorized to experiencemedia content 2001-N. If system 210 and the user thereof are authorizedto experience media content 2001-N, secure media player 1210 commencesto render the media content for presentation via media hardware outputdevice 1370.

Concurrent with rendering media content 2001-N, secure media player1210, can, in one embodiment, communicate with server 250 and/or 251 andretrieve the decryption key associated with each encryption, e.g.,1351-1N, and with decrypter 1211 of FIG. 12, dynamically decrypt eachinstance of media, e.g., 2001-N, as the content is being rendered andoutput via line 1574 to media hardware output device 1370.

Because rendered content is vulnerable to capture and/or imaging, andthus becoming subject to ripping, burning, copying, and the like, securemedia player 1210 can watermark, via watermarker 1212 the outgoing datastream that is output to media hardware output device 1370 via line1574. In one embodiment, utilizing watermarker 1212, the outgoing datastream is watermarked concurrent with the rendering performed by securemedia player 1210. Further, secure media player 1210 attaches a uniqueidentifier with each rendered media content 2001-N. In one embodiment,serial number 1380 is attached to each media content 2001-N, as it isbeing rendered and output to media hardware output device 1370. In thismanner, if the rendered content being output is somehow captured,imaged, etc., by virtue of the association of serial number 1380 withmedia storage device 999 and the media content disposed thereon, e.g.,content 2001-N, and the computer system 210 with which the recipient ofmedia storage device 999 is associated, unauthorized presentation andreproduction of the media content is prevented.

FIG. 16 is a flowchart 1600 of computer implemented steps performed inaccordance with one embodiment of the present invention for controllingpresentation of media content disposed on a media storage device.Flowchart 1600 includes processes of the present invention, which, inone embodiment, are carried out by processors and electrical componentsunder control of computer readable and computer executable instructions.The computer readable and computer executable instructions reside, forexample, in data storage features such as computer usable volatilememory 104 and/or computer usable non-volatile memory 103 of FIG. 1.However, the computer readable and computer executable instructions mayreside in any type of computer readable medium. Although specific stepsare disclosed in flowchart 1600, such steps are exemplary. That is, thepresent invention is well suited to performing various other steps orvariations of the steps recited in FIG. 16. Within the presentembodiment, it should be appreciated that the steps of flowchart 1600may be performed by software, by hardware or by any combination ofsoftware and hardware.

It is noted that flowchart 1600 is described in conjunction with FIGS.2, 3, 4, 5A-5D, 6, 7A-7C, 8-15 to more fully describe the operation ofthe present embodiment. In step 1610, an autorun mechanism disposed on amedia storage device 999, e.g., autorun protocol 910, is activated inresponse to a computer system 210 receiving media storage device 999 inan appropriate device drive, e.g., media storage device drive 1112.

In step 1612 of FIG. 16, a monitoring program within UCM 1200 disposedon media storage device 999 determines if a usage compliance mechanism,e.g., UCM 1200, is installed on the computer system which received mediastorage device 999, e.g., computer system 210. In one embodiment, agentprograms 304 may perform the determination. However, in anotherembodiment, combinations of components of a CCM 300, as described hereinwith reference to FIG. 3, 4, 7A-7C may be utilized.

If UCM 1200 is not present on computer system 210, the present methodproceeds to step 1611. Step 1611 installs a usage compliance mechanismon computer system 210, as described herein with reference to FIGS. 3,4, 5A-5D, 6, 7A-7C, and 8-15. Alternatively, if UCM 1200 is present oncomputer system 210, the present method proceeds to step 1614.

In step 1614, a monitoring mechanism within UCM 1200 disposed on mediastorage device 999 determines if a secure media player 1210 is presentand operable on computer system 210. In one embodiment, agent program304 of CCM 300 of FIG. 3 can provide the determination.

If a secure media player 1210 is not present and operable on computersystem 210, the present method proceeds to step 1611. Step 1611 installsa secure media player 1210 on computer system 210, as described hereinwith reference to FIGS. 3, 4, 5A-5D, 6, 7A-7C, and 8-15. It is notedthat if usage compliance mechanism 1200 and/or secure media player 1210cannot be properly installed on computer system 210, the present methodproceeds to step 1622, which ends the session and which preventscomputer system 210 from presenting the content on media storage device999. Alternatively, if a secure media player 1210 is present andoperable on computer system 210, the present method proceeds to step1616.

In step 1616, UCM 1200 communicates with servers 250 and/or 251 innetworks 200, 400, 1000, and/or 1400 and determines whether computersystem 210 and the user thereof are authorized to experience mediacontent 2001-N on media storage device 999, as described herein withreference to FIGS. 3, 4, steps 704-708 of FIGS. 7A and 8-15. If computersystem 210 and the user thereof are not authorized to experience thecontent on media storage device 999, the present method proceeds to step1615. Alternatively, if computer system 210 and the user thereof areauthorized to experience the content on media storage device 999, thepresent method proceeds to step 1618.

In step 1618 of FIG. 16, UCM 1200 determines if secure media player1210, usage compliance mechanism 1200 and computer system 210 are allcommunicatively coupled with networks 200, 400, 1000, and/or 1400. Ifone or more of the conditions are not met, the present method proceedsto step 1615. Alternatively, if secure media player 1210, usagecompliance mechanism 1200, and computer system are all communicativelycoupled with networks 200, 400, 1000, and/or 1400, the present methodproceeds to step 1620.

Step 1615 of FIG. 16 prevents presentation of content on a media storagedevice, e.g., media content 2001-N on media storage device 999, to theuser of computer system 210. Alternatively, computer system 210 and theuser thereof may communicate with networks 200, 400, 1000, and/or 1400and attempt to establish credentials and/or to re-establish acommunicative coupling with networks 200, 400, 1000, and/or 1400, thatwould allow presentation of the content, as described herein withreference to FIG. 3, 4, and steps 704-708 of FIG. 7A.

In step 1620, media content 2001-N on media storage device 999 is readby media storage device drive 1112. File system filter driver 1220intercepts the read operation being performed by media storage devicefile system driver 1114 and dynamically decrypts a second encryptionapplied to media content 2001-N, e.g., encryptions 2351-2N of FIG. 13,via decrypter 1221 and a second decryption key stored on and retrievedfrom servers 250 and/or 251. It is noted that if file system filterdriver 1220 is not communicatively coupled with server 250 and/or 251,enabling retrieval of the second decryption key, presentation of thecontent on a media storage device 999 is not permitted.

Continuing with step 1620 of FIG. 16, subsequent to second encryption2351-2N being decrypted, media content 2001-N, still encrypted with afirst encryption, e.g., encryptions 1351-1N, respectively, is output tosecure media player 1210. In one embodiment, secure media player 1210,in conjunction with UCM 1200, communicates with server 250 and/or 251and commences to render the media content for presentation via mediahardware output device 1370.

Concurrent with rendering media content 2001-N, secure media player1210, can, in one embodiment, communicate with server 250 and/or 251 andretrieve the decryption key associated with each encryption, e.g.,1351-1N, and with decrypter 1211 of FIG. 12, dynamically decrypt eachinstance of media, e.g., 2001-N, as the content is being rendered andoutput the rendered content to media hardware output device 1370.

Because rendered content is vulnerable to capture and/or imaging, andthus becoming subject to ripping, burning, copying, and the like, securemedia player 1210 can watermark, via watermarker 1212, the outgoing datastream that is output to media hardware output device 1370. In oneembodiment, the outgoing data stream is watermarked concurrent with therendering performed by secure media player 1210. Further, secure mediaplayer 1210 attaches a unique identifier with each rendered mediacontent 2001-N. In one embodiment, serial number 1380 is attached toeach media content 2001-N, as it is being rendered and output to mediahardware output device 1370. In this manner, if the rendered contentbeing output is somehow captured, imaged, etc., by virtue of theassociation of serial number 1380 with media storage device 999 and themedia content disposed thereon, e.g., content 2001-N, and the computersystem 210 with which the recipient of media storage device 999 isassociated, unauthorized presentation and reproduction of the mediacontent is prevented.

In another implementation, embodiments of the present invention can beutilized in a distributed network topology to control media sharingamong computer system within the network. Some of the distributednetwork topologies in which embodiments of the present invention can beutilized are, but is not limited to, a centralized, a ring, ahierarchical, and a decentralized distributed topology. A decentralizeddistributed network topology is commonly referred to as a peer-to-peer(P2P) network. In a P2P network, each computer system/node in thenetwork is able to communicate with any other computer system/nodewithin the network. A computer system in a P2P network can request datafrom the network as well as provide data to the network. Thus, acomputer system can be both a requesting computer system (requestingnode) and a source computer system (source node) within a P2P network.Additionally, there may be a host server or a plurality of host serverspresent in the network that may be utilized alone or in combination witheach other (e.g. as an administrative node, supemode, etc.) to provideadministrative functionalities to the computer systems therewithin andfor providing content to the P2P network.

It is known that many implementations of a distributed network topology,e.g., a decentralized topology, are not configured to adequately controland/or monitor the exchanging or trading of media among computer systemsin the P2P network. Embodiments of the present invention provide a noveland inventive solution to this problem.

FIG. 17 is a block diagram of a network environment 1700 for sharingmedia content between the computer systems communicatively coupledtherewith, in one embodiment of the present invention. Network 1700includes a client computer system 1705, a source computer system 1715and a server computer system 1770, which are communicatively coupled viacommunication link 1710. Communication link 1710 may be a wireline,wireless, or combination of wireline and wireless technologies andcommunication protocols that facilitate interaction between computersystems. Additionally, in the present embodiment, systems 1705, 1715,and 1770 may each implemented in a similar manner as described hereinwith reference to FIG. 1. Further, network environment 1700 may beimplemented in a manner similar as described herein with reference tonetwork 200 of FIG. 2 and network 800 of FIG. 8.

In one embodiment, client computer system 1705 may be implemented in amanner similar to a client computer system 210 as described herein withreference to FIGS. 2, 4-8, 10, 11, 14, and 15. Source computer system1715 may, in one embodiment, be a client computer system 1705 that makesavailable to network 1700 media content that may be stored therewithin.In another embodiment, source computer system 1705 may be a mediadistribution point (MDP) as described herein with reference to FIG. 8,configured to make available to network 1700 media content that may bestored therewithin. By virtue of the functionality inherent to a P2Pnetwork, source computer system 1715 can be a client computer system1705 and client computer system 1705 can be a source computer system1715.

Still referring to FIG. 17, server computer system 1770 may, in oneembodiment, be implemented in a manner similar to a web server 250and/or content server 251, as described herein with reference to FIGS. 2and 4. As such, server computer system 1770 may also be coupled to adatabase, e.g., database 451 and/or 451 of FIG. 4. Accordingly, servercomputer system 1770 can, in one embodiment, be configured to providemanagement functionalities to a network, e.g., network 1700 or network800 of FIG. 8. Types of management functionalities that can be providedby server computer system 1770 can include, but is not limited to,network management, user management, encryption and decryption keymanagement, authorization management, media management, transactionmanagement, player application management, and cache management. Servercomputer system 1770 can also be implemented as a source computer system1715 and/or as a media delivery point as described herein with referenceto FIG. 8.

Network management can include, but is not limited to, determining theroute through which an instance of media is transferred to anothercomputer system in network 1700. For example, and referring to FIG. 8,an instance of media is located in plurality of locations within network800, e.g., media delivery points 808 (San Jose), 816 (Tokyo), and 812(New York City). Client computer system 1705 located in Washington D.C.requests that particular instance of media content. Server computersystem 1770 is able to determine, for this example, that the leastamount of network resources needed to transfer the media content torequesting client computer system 1705 would be transferring theinstance of media content from media delivery point 812 (New York City).

It is anticipated that many instances of a particular instance of mediamay be disposed throughout the network, e.g., network 1700, in whichthere may be varying degrees of quality among the instances mediacontent. Further, it is known that differing source computer systems1715 can have varying rates of transfer, e.g., a source computer system1715 may be coupled to network 1700 via a digital subscriber line (DSL),whereas another source computer system 1715 may be coupled to network1700 via 56K modem, which is substantially slower than a DSL connection.Additionally, transfer routes that would go through a network connectionthat may be experiencing downtime or technical difficulties can bererouted. Advantageously, server computer system 1770 can incorporatequality of media content, connection health, and/or delivery speedinformation into its determination from which source computer system1715 the instance of media is to be delivered.

Still referring to FIG. 17, user management, in one embodiment, caninclude, but is not limited to, maintaining and verifying current userinformation, e.g., user name, password, billing address, valid creditcard number, valid online payment or alternative electronic paymentservice, mac address, etc., as described herein with reference to FIGS.3 and 4, and steps 704-710 of FIGS. 7A-7C.

In one embodiment, encryption and decryption key management includes,but is not limited to, storing an encryption key associated with aclient computer system for use by the client computer system to encryptmedia content thereon into an encryption local to that client computersystem, managing a plurality of intermediate encryption and decryptionkeys for utilization with media content that is being transmitted to aclient computer system, etc.

In one embodiment, authorization management may include verifying that aclient computer system 1705 is authorized to be connected to network1700, thus being associated with the network. Alternatively,authorization management may also include, but is not limited to,authorizing/prohibiting sharing of an instance of media with network1700 that does/does not comply with copyright restrictions or licensingagreements applicable to the particular instance of media.

Still referring to FIG. 17, media management can include, but is notlimited to, storing a list of available instances of media content andits associated location within network 1700, storing information relatedto each instance of media, e.g., title, artist, genre, length/durationof media content, bit pattern information related to a particularinstance of media for identification, storing information regardingroyalty fees (where applicable) that may be assessed to an instance ofmedia content each time it is transmitted within the network, storinginformation to enable expiring the media content on a computer systemwhen the computer system is no longer authorized to access and/or is nolonger associated with network 1700, and the like.

Additionally, media management can also include utilizing an ethernetfilter and other mechanisms to obtain information related to transmittedand/or received instances of media, instances of media that haverecently entered the network, and the like. In one embodiment, anethernet filter may be coupled to a network interface device (e.g.,modem, NIC, wireless receiver, etc.) coupled to the computer systemreceiving the instance of media content e.g., signal device 104 coupledto computer system 100 of FIG. 1. Information obtained by an ethernetfilter can be used in identifying a particular instance of media,determining appropriate royalty fees, etc.

In one embodiment, transaction management can include generating atransaction for each successful transfer of media content from onecomputer system to another computer system in the network, e.g., fromsource computer system 1715 to client computer system 1705 in network1700. In one embodiment, the receiving client computer system 1705acknowledges successful receipt of the media content and accordingly,server computer system 1770 generates a transaction applicable to thereceiving computer system and which is associated with that particularinstance of media. Because different instances of media content may havediffering usage and/or royalty fees associated therewith, embodiments ofthe present invention provide the mechanisms to account for eachtransfer, generate a transaction for each transfer, and generate apayment from the recipient of the instance of media, and, in oneembodiment, deliver an appropriate remuneration to the media contentcopyright holder.

Advantageously, a royalty transaction can also be applied to acopyrighted instance of media where no royalty payment was previouslypossible. For example, assume that a bootleg copy of an artist's liveperformance has been freely available for years. This bootleg copy mayhave been made from a portable recorder brought into a live performanceand was used to record the performance. In this example, a personacquires an analog bootleg copy and converts it to a digital format oracquires a digital format of the bootleg copy. The digital copy is thenavailed to network 1700 for sharing among the computer system coupledtherewith. It is noted that when an instance of media enters network1700, it becomes protected as described herein with reference to FIGS.3, 4-9, 11, 12, and 15.

Accordingly, when a client computer system 1705 successfully receivesthe digital copy, a transaction is generated, thus invoking a royaltypayment when no such royalty payment was previously possible.Advantageously, this can provide a means to distribute appropriateremunerations to copyright holders and licensees that would otherwisereceive no payment.

Continuing, when an instance of media can be freely distributed, atransaction is still generated. This advantageously provides a record ofthe numbers of requests for a particular instance of media, the locationfrom where those requests originated, and the like, thereby providingdata which can be utilized in marketing studies and implementingmarketing strategies, etc.

It is particularly noted that in an alternative implementation,embodiments of the present invention can be readily configured toprovide a mechanism that can generate a sales/use tax transactionrelated to transfer of a instance of media. Embodiments of the presentinvention can be readily configured to calculate appropriate sales/usetax amounts relative to the location of the receiving client computersystem. Advantageously, this would enable municipalities, counties,states, and other governmental agencies to increase revenue, thuspossibly realizing a reduction in a deficit associated with agovernment. It is anticipated that generating sales/use tax transactionscould provide from tens to hundreds of millions of dollars in previouslyuntapped revenue to those governmental agencies.

Still referring to FIG. 17, player management, in one embodiment, caninclude, but is not limited to, maintaining secure player applicationintegrity, adding additional player applications to a list of approvedplayer applications, removing player applications that do not meet usagerestriction requirements applicable to a media file, modification of asecure player application to improve its functionality, modification tocounteract nefarious hacking attempts, disabling the secure playerapplication when the computer system on which it is operable is nolonger authorized to participate in or is associated with network 1700,etc.

Cache management, in one embodiment, can include, but is not limited to,maintaining protected media container file integrity, modificationthereof to improve functionality or to counteract detected nefariousactivities, disabling the protected media container file when thecomputer system upon which the protected media container file isdisposed is not authorized to access and/or is no longer associated withnetwork 1700.

In the present embodiment, client computer system 1705 and sourcecomputer system 1715 each have an instance of a usage compliancemechanism (UCM) 1800 coupled therewith. In the present embodiment, UCM1800 of FIG. 17 and as described with detail in FIG. 18 is similar to acopyright compliance mechanism 300 and/or a usage compliance mechanism900 and/or 1200, as described herein with reference to FIGS. 3, 4,5A-5D, 6A, and/or 9, 11, 12, and 15, respectively.

FIG. 18 is a block diagram of components in a usage compliance mechanism(UCM) 1800 that is configured to be installed and operable on a clientcomputer system 1705 and/or a source computer system 1715 of FIGS. 17and 19, in one embodiment of the present invention. In the presentembodiment, UCM 1800 includes a copyright compliance mechanism 300analogous to a copyright compliance mechanism 300 as described hereinwith reference to FIGS. 3, 4, 5A-5D and 6A. It is noted that UCM 1800also includes those features and components as provided in a UCM 900 anda UCM 1200 as described herein with reference to FIGS. 9, 11, 12, and15, respectively.

In the present embodiment, UCM 1800 further includes a secure playerapplication 1810, a client communication application 1820, and a mediastorage container creator 1830. Media storage container creator 1830 isconfigured to allocate a portion of a memory unit coupled to thecomputer system in which UCM 1800 is installed, e.g., volatile memory102 and/or non-volatile memory 103 of computer system 100 of FIG. 2.Media storage container creator 1830 utilizes the allocated portion of amemory unit and creates a protected media container file (e.g., a customfile system) into which received and/or availed instances of media,e.g., audio files, video files, multimedia files, documents, software,and the like, are stored. It is noted that in one embodiment, mediacontent that is stored in a protected media contain file is, in additionto other encryptions applicable to the instance of media, encryptedlocal to the computer system on which the protected media file containeris disposed. In an example, an instance of media 9090 is stored on bothclient computer system 1705 and source computer system 1715 of FIG. 17.Accordingly, media content 9090 is uniquely encrypted local to system1705 and is uniquely encrypted local to system 1715. Additionally, inthe context of the present invention, the term availed and/or availingrefers to making available to a network, e.g., network 1700, an instanceof media that may be stored in a protected media container file.

Still referring to FIG. 18, UCM 1800 also includes, in one embodiment, aclient communication application 1820. Client communication applicationis a custom client communication application configured to providecommunication functionality between the nodes in a decentralizeddistributed network, e.g., network 1700. Alternatively, clientcommunication application 1820 is also well suited to be implemented innearly any network, including, but not limited to, network 1700. Clientcommunication application 1820 can be a well known and readily availablecommunication application and which may be written in a commonlyutilized programming language including, but not limited to, C, C++,Java, Fortran, etc.

In one embodiment, client communication application 1820 is configuredto decrypt media content from an encryption local to a computer systemon which application 1820 is operable. Client communication application1820 is also configured to encrypt media content into an intermediateencryption for transferring the media content to another computer systemcommunicatively coupled with a network, e.g., network 1700. Application1820 is additionally configured to decrypt media content that isreceived in an intermediate encryption from a computer system coupledwith network 1700. Client communication application 1820 is furtherconfigured to encrypt the media content into an encryption local to thecompute r system on which application 1820 is operable.

In one embodiment, client communication application 1820 can utilize anintermediate encryption key provided by a server computer system, e.g.,server 1770 of FIG. 17, to encrypt the media content into theintermediate encryption for transfer. Application 1820 can also utilizean intermediate decryption key, also provided by server 1770, to decryptmedia content that is received in an intermediate encryption from acomputer system coupled with network 1700.

In one embodiment, client communication application 1820 can transmit anacknowledge signal or indicator indicating that the media contentdelivered from another computer system in network 1700 was successfullyreceived. In one embodiment, an acknowledge signal received by servercomputer 1770 can generate a transaction applicable to the computersystem receiving the media content and which is associated with themedia content that was received.

Still referring to FIG. 18, UCM 1800 further includes a secure playerapplication 1810 configured to access contents of a protected mediacontainer file, e.g., an instance of media, and is also configured toprovide presentation of the media content to the computer system onwhich the media content is stored. Secure player application 1810 isfurther configured to utilize its access to the protected mediacontainer file and make available to the network the contents thereof.In one embodiment, secure player application 1810 can present the mediacontent to the computer system on which it is operable while thecomputer system is offline, e.g., not coupled with network 1700 butstill associated therewith.

Secure player application 1810 can be media type specific, meaning thatthere may be a secure audio player application for audio files, a securevideo player application for video files, a secure alphanumericapplication for text files, a secure software player application forsoftware files, and so on. It is noted that secure player application1810 can be configured to interact with nearly any media type.

In one embodiment, secure player application 1810 can be a custom mediadevice 310 which can be an emulation of a custom media device driver 307as described herein with reference to FIGS. 3, 4, and FIGS. 5A-5D. Inanother embodiment, secure player application 1810 can be an approvedplayer application as described herein with reference to FIG. 3.

FIG. 19 is an exemplary system 1900 for controlling media sharing amongmultiple computer systems communicatively coupled in a network inaccordance with one embodiment of the present invention.

System 1900 includes a client computer system 1705 analogous to clientcomputer system 1705 of FIG. 17, a server computer system 1770 analogousto server computer system 1770 of FIG. 17, and a source computer system1715 analogous to source computer system 1715 of FIG. 17. Systems 1705,1715 and 1770 are implemented in and communicatively coupled to anetwork 1700 in one embodiment of the present invention. In oneembodiment, network 1700 is a decentralized distributed network, e.g.,network 800 of FIG. 8.

In an implementation, source computer system 1715 and client computersystem 1705 have logged on to network 1700, as described herein withreference to FIGS. 4, and steps 702-716 of FIG. 7A. Client computersystem 1705 requests an instance of media from network 1700, e.g.,instance of media 4321, shown as communication 1810. Network 1700receives the request and server computer system 1770 determines thelocation of an instance of media 4321. Server computer system 1770responds to client computer system 1705 with the location of instance ofmedia 4321, shown as communication 1820.

In this example, server computer system 1770 is cognizant that sourcecomputer system 1715 has an instance of media 4321 disposed therein. Inthe present embodiment, instance of media content 4321 is stored in aprotected media container file on a memory unit coupled to sourcecomputer system 1715. Additionally, instance of media 4321 is encryptedlocal to source computer system 1715, shown as dotted line 1716encompassing media 4321.

Continuing, source computer system 1715 sends a request to servercomputer system 1770 for an intermediate encryption key to encryptinstance of media 4321 for transfer to client computer system 1705,shown as communication 1830. Server computer system 1770 transmits anintermediate encryption key, e.g. key 1775, to source computer system1715. Upon receipt of intermediate encryption key 1775 by sourcecomputer system 1715, a client communication application 1820 operableon source computer system 1715 decrypts media 4321 from its encryptionlocal thereto, e.g., encryption 1716, and encrypts media 4321 into anintermediate encryption, as indicated by dotted line 1775 encompassingmedia 4321.

Still referring to FIG. 19, once source computer system 1715's clientcommunication application 1820 encrypts media 4321 into intermediateencryption 1775, client communication application 1820 transmits media4321 in intermediate encryption 1775 to client computer system 1705,shown as communication 1850. Upon client computer system 1705 receivingmedia 4321 in intermediate encryption 1775, client computer system 1705sends a request to server computer system 1770 for an intermediatedecryption key e.g., key 1776, shown as communication 1860. Intermediatedecryption key 1776 enables a client communication application 1820operable on client computer system 1705 to decrypt media 4321 from itsintermediate encryption 1775. It is noted that until intermediateencryption 1775 is decrypted, secure player 1810 operable on clientcomputer system 1705 is unable to present media 4321 to system 1705. Itis further noted that if another computer system in network 1700 hasintercepted media 4321 during transfer, the intermediate encryption 1775prevents use of media 4321 by the intercepting computer system.

Continuing, server computer system 1770 responds to client computersystem 1705's request for an intermediate decryption key and transmitskey 1776 to client computer system 1705, shown as communication 1870.Once key 1776 is received by client computer system 1705, a clientcommunication application 1830 operable on system 1705 decrypts media4321 out of intermediate encryption 1775 and encrypts media 4321 into anencryption local to client computer system, e.g., encryption 1776encompassing media 4321.

When media 4321 has been successfully received by and encrypted into anencryption local to client computer system 1705, e.g., media 4321 withencryption 1706, client computer system 1705 transmits an acknowledgeindicator indicating successful receipt of media 4321, shown ascommunication 1880. Accordingly, upon receipt of an acknowledgeindictor, server computer system 1770 generates a transaction applicableto client computer system 1705 and which is associated with media 4321.

Advantageously, embodiments of the present invention provide componentsthat enable controlled media sharing in a decentralized distributednetwork (a p2p network), e.g., network 800 of FIG. 8 and/or network 1700of FIG. 17. Further advantageous is that embodiments of the presentinvention can also track the sharing, generate royalties applicable to areceiving computer system and associated with a particular instance ofmedia. Also advantageous is that embodiments of the present inventionallow for outside instances of media to enter the network and providecompliance with copyright restrictions and licensing agreementsassociated with the instance of media.

The foregoing disclosure regarding specific embodiments of the presentinvention have been presented for purposes of illustration anddescription. They are not intended to be exhaustive or to limit theinvention to the precise forms disclosed, and many modifications andvariations are possible in light of above teaching. The embodiments werechosen and described in order to best explain the principles of theinvention and its practical application, to thereby enable othersskilled in the art to best utilize the invention and various embodimentswith various modifications as are suited to the particular usecontemplated. It is intended that the scope of the invention be definedby the Claims appended hereto and their equivalents.

1. A method of controlled media sharing among a plurality of nodes in a network, said method comprising: initiating a search for an instance of media content available from said network, wherein a node communicatively coupled with said network initiates said search; receiving a source location of said instance of media content from an administrative node coupled to said network; requesting from said source location said instance of media content; and receiving said instance of media content from said location, wherein said instance of media content is decrypted from an encryption local to said source location and encrypted in an intermediate encryption prior to delivery to said node.
 2. The method as recited in claim 1 further comprising: requesting from said administrative node an intermediate decryption key for decrypting said intermediate encryption of said instance of media content.
 3. The method as recited in claim 2 further comprising: decrypting said intermediate encryption utilizing said intermediate decryption key and encrypting said instance of media content into an encryption local to said node, said decrypting and encrypting performed by a client application coupled to said node.
 4. The method as recited in claim 1 further comprising: sending an acknowledgement indicator to said administrative node to indicate said instance of media content was successfully received by said node, wherein said acknowledgement indicator generates a transaction applicable to said node and associated with said instance of media content, said transaction in said administrative node.
 5. The method as recited in claim 1 further comprising: storing said instance of media content in an custom file system on a memory unit coupled to said node, wherein said instance of media content is stored in an encryption local to said node.
 6. The method as recited in claim 1 further comprising: availing to said network said instance of media content via a secure player coupled to said node.
 7. The method as recited in claim 6 further comprising: disabling said secure player when said node is no longer associated with said network, said disabling preventing said node from availing said instance of media content to said network.
 8. The method as recited in claim 6 further comprising: enabling said secure player application to present said instance of media content on said node to said node while said node is not in said plurality and while said node is associated with said network.
 9. The method as recited in claim 6 further comprising: preventing said secure player application from presenting said instance of media content stored on said node to said node when said node is no longer associated with said network.
 10. The method as recited in claim 1 further comprising: complying with a usage restriction applicable to said instance of media content via a usage restriction mechanism coupled to said node.
 11. A system for controlled media sharing among a plurality of nodes in a network comprising: a node coupled with said plurality of nodes, said node enabled to request an instance of media content from said network; a client application coupled to said node, said client application to enable communication between said node and said plurality of nodes; and wherein said instance of media content is received by said node from a source node in said plurality of nodes, said instance of media content decrypted from an intermediate encryption and encrypted into an encryption local to said node, said instance of media presentable on said node via a secure player application installed and operable thereon.
 12. The system as recited in claim 11 wherein said client application is configured to request from an administrative node coupled to said network an intermediate decryption key, said intermediate decryption key to enable said client application to decrypt said instance of media content in said intermediate encryption.
 13. The system as recited in claim 12 wherein said client application is further configured to decrypt said instance of media content in said intermediate encryption utilizing said intermediate decryption key and is further configured to encrypt said instance of media content into said encryption local to said node.
 14. The system as recited in claim 11 wherein said client application is further configured to transmit to an administrative node in said plurality of nodes an indicator indicating said instance of media content was successfully received by said node, said indicator generating a transaction applicable to said node and associated with said instance of media content and performed by said administrative node.
 15. The system as recited in claim 11 wherein said node further comprises a custom file system disposed on a memory unit coupled thereto into which said instance of media content is stored.
 16. The system as recited in claim 11 wherein said secure player is configured to avail to said plurality of nodes said instance of media content.
 17. The system as recited in claim 16 wherein said secure player is further configured to be disabled to prevent availing of said instance of media content to said plurality of nodes when said node is no longer associated with said network.
 18. The system as recited in claim 16 wherein said secure player application is configured to be disabled to prevent presentation of said instance of media content on said node to said node when said node is no longer associated with said network.
 19. The system as recited in claim 16 wherein said secure player application is configured to present said instance of media content on said node to said node when said node is not in said plurality of nodes and while said node is associated with said network.
 20. The system as recited in claim 11 wherein said source node and an administrative node are the same node in said plurality of nodes.
 21. The system as recited in claim 11 wherein a usage compliance mechanism is coupled to said node for providing compliance with a usage restriction applicable to said instance of media content.
 22. A computer readable medium for storing computer implemented instructions, said instructions for causing anode in a plurality of nodes to perform a method of controlled media sharing among said plurality of nodes in a network, said method comprising: requesting an instance of media content from said network, said request from said computer system, said computer system a node in said plurality of nodes; receiving said instance of media content from a source node in said plurality of nodes, wherein said instance of media content is received in an intermediate encryption; and decrypting said instance of media content from said intermediate encryption and encrypting said instance of media content in an encryption local to said node.
 23. The computer readable medium of claim 22 wherein said method further comprises transmitting from said node to an administrative node in said plurality of nodes an indicator indicating successful receipt of said instance of media content, said indicator invoking a transaction applicable to said node and associated with said instance of media content.
 24. The computer readable medium of claim 22 wherein said method further comprises storing said instance of media content in a custom file system on a memory unit coupled with said node.
 25. The computer readable medium of claim 24 wherein said method further comprises availing to said network said instance of media content.
 26. The computer readable medium of claim 22 wherein said method further comprises requesting from an administrative node in said plurality of nodes an intermediate decryption key for said decrypting of said instance of media content in said intermediate encryption.
 27. The computer readable medium of claim 22 wherein a client application coupled to said node performs said decrypting and said encrypting.
 28. The computer readable medium of claim 22 wherein a secure player application coupled to said node is configured to avail said instance of media content to said network.
 29. The computer readable medium of claim 28 wherein said method further comprises disabling said secure player application to prevent availing of said instance of media content to said plurality of nodes when said node is no longer associated with said network.
 30. The computer readable medium of claim 28 wherein said method further comprises preventing said secure player application from presenting said instance of media content on said node when said node is no longer associated with said network.
 31. The computer readable medium of claim 28 further comprising enabling said secure player application to present said instance of media content on said node to said node while said node is not in said plurality of nodes and while said node is associated with said network.
 32. The computer readable medium of claim 22 wherein said method further comprises complying with a usage restriction applicable to said instance of media content via a usage compliance mechanism coupled to said node. 